Triple
T36846739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam Stand |
E910567
|
entity |
| Predicate | belongsToStadiumComplex |
P38286
|
FINISHED |
| Object | Estadio Centenario complex |
—
|
NE NERFINISHED |
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: Estadio Centenario complex | Statement: [Amsterdam Stand, belongsToStadiumComplex, Estadio Centenario complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToStadiumComplex Context triple: [Amsterdam Stand, belongsToStadiumComplex, Estadio Centenario complex]
-
A.
belongsToStadiumType
Indicates that a stadium is classified as being of a particular stadium type.
-
B.
containsStadium
Indicates that a location or area includes a stadium within its boundaries or premises.
-
C.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific stadium.
-
D.
associatedStadiums
Indicates that there is a relationship linking an entity to one or more stadiums with which it is connected or affiliated.
-
E.
belongsToBuildingComplex
chosen
Indicates that one building or structure is part of, or included within, a larger building complex.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
Created at: May 3, 2026, 4:13 p.m.