Triple
T27366665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cúcuta |
E690182
|
entity |
| Predicate | mainSportVenue |
P72058
|
FINISHED |
| Object | Estadio General Santander |
—
|
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 General Santander | Statement: [Cúcuta, mainSportVenue, Estadio General Santander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSportVenue Context triple: [Cúcuta, mainSportVenue, Estadio General Santander]
-
A.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
B.
ownsSportsVenue
Indicates that one entity possesses legal ownership or controlling property rights over a sports venue used for athletic or sporting events.
-
C.
sportsVenueLocatedIn
Indicates that a sports venue is geographically situated within a specified location or administrative area.
-
D.
gameVenue
Indicates the location or facility where a game or match is held.
-
E.
typicalVenueStadium
chosen
Indicates that the usual or characteristic venue for the referenced activity, event, or entity is a stadium.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 12:17 p.m.