Triple
T13381993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmed bin Ali Stadium |
E319339
|
entity |
| Predicate | worldCupMatchesHosted |
P85436
|
FINISHED |
| Object | group stage |
—
|
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: group stage | Statement: [Ahmed bin Ali Stadium, worldCupMatchesHosted, group stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldCupMatchesHosted Context triple: [Ahmed bin Ali Stadium, worldCupMatchesHosted, group stage]
-
A.
fifaWorldCupMatchesHosted
chosen
Indicates that an entity (typically a country, city, or stadium) has hosted one or more official FIFA World Cup matches.
-
B.
worldCupPlayed
Indicates that a World Cup tournament has taken place or been held (typically at a specific time and/or location).
-
C.
worldCupHost
Indicates that one entity serves as the host country or location for a particular FIFA World Cup tournament.
-
D.
RugbyWorldCupHosts
Indicates that the specified country (or countries) served as the official host nation(s) for a particular edition of the Rugby World Cup.
-
E.
worldCupHostYear
Indicates the year in which a particular country or location served as the host of the FIFA World Cup tournament.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce694788190881d1feac5b75720 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:33 p.m.