Triple
T24422740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiento |
E615767
|
entity |
| Predicate | locationOfHistoricUse |
P46887
|
FINISHED |
| Object | Estadio Centenario |
—
|
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 | Statement: [Tiento, locationOfHistoricUse, Estadio Centenario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfHistoricUse Context triple: [Tiento, locationOfHistoricUse, Estadio Centenario]
-
A.
historicalLocationOf
chosen
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
B.
primaryLocationHistoric
Indicates the historically primary or most significant location associated with an entity, such as where it was originally based, founded, or chiefly active in the past.
-
C.
locatedInHistoricContext
Indicates that an entity is situated within or associated with a historically significant setting, period, or environment.
-
D.
historicallyLocatedNear
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
E.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a4285881909376560f1cf4bf62 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.