Triple
T1047335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vålerenga Fotball |
E22610
|
entity |
| Predicate | usesStadiumFor |
P10029
|
FINISHED |
| Object | home matches |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: home matches | Statement: [Vålerenga Fotball, usesStadiumFor, home matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStadiumFor Context triple: [Vålerenga Fotball, usesStadiumFor, home matches]
-
A.
containsStadium
Indicates that a location or area includes a stadium within its boundaries or premises.
-
B.
locatedInStadium
Indicates that an entity is situated within or at the premises of a specific stadium.
-
C.
playedAtStadium
chosen
Indicates that an event or game took place at, or was hosted in, a specific stadium.
-
D.
usesStadiumAsOffice
Indicates that an entity utilizes a stadium facility as its primary place of business or administrative operations.
-
E.
stadium
Indicates that an entity is a sports or event venue where games, competitions, or large gatherings take place.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.