Triple
T10064025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arena da Amazônia |
E213054
|
entity |
| Predicate | FIFAStadiumCategory |
P91907
|
FINISHED |
| Object | FIFA World Cup venue |
—
|
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: FIFA World Cup venue | Statement: [Arena da Amazônia, FIFAStadiumCategory, FIFA World Cup venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIFAStadiumCategory Context triple: [Arena da Amazônia, FIFAStadiumCategory, FIFA World Cup venue]
-
A.
UEFAStadiumCategory
Indicates the classification of a stadium according to UEFA’s official stadium category standards and requirements.
-
B.
stadiumFeature
Indicates that a stadium possesses or includes a particular feature, characteristic, or facility.
-
C.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
D.
footballStadiumLocation
Indicates the relationship specifying where a particular football stadium is geographically located.
-
E.
stadium
Indicates that an entity is a sports or event venue where games, competitions, or large gatherings take place.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd653748190aeddf7a679028604 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:58 p.m.