Triple
T14510519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalifa International Stadium |
E340382
|
entity |
| Predicate | FIFAWorldCupVenue |
P114512
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Khalifa International Stadium, FIFAWorldCupVenue, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIFAWorldCupVenue Context triple: [Khalifa International Stadium, FIFAWorldCupVenue, 2022]
-
A.
WorldCupVenueSince
Indicates that a location has served as a venue for World Cup events starting from a specified point in time.
-
B.
FIFAStadiumCategory
Indicates the classification level or category assigned to a stadium according to FIFA’s official stadium standards and requirements.
-
C.
footballStadiumLocation
Indicates the relationship specifying where a particular football stadium is geographically located.
-
D.
associatedWithCountryStadium
Indicates that there is an association or connection between a country and a stadium, such as location, ownership, or primary use.
-
E.
countryNationalStadiumOf
Indicates that a given stadium serves as the official national stadium of a specified country.
- F. None of above. chosen
Provenance (4 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e5b7b48190878be271840c265b |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.