Triple
T24348719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estadio Azul |
E613721
|
entity |
| Predicate | neighbouringFacility |
P5648
|
FINISHED |
| Object | Plaza de Toros México |
—
|
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: Plaza de Toros México | Statement: [Estadio Azul, neighbouringFacility, Plaza de Toros México]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighbouringFacility Context triple: [Estadio Azul, neighbouringFacility, Plaza de Toros México]
-
A.
neighboringProvision
Indicates that one entity provides resources, services, or support to another entity located nearby or in an adjacent area.
-
B.
adjacentFacilitySecurityClass
Indicates that two facilities located next to each other share a specified level or classification of security.
-
C.
hasNearbyFacility
chosen
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
D.
hasSiblingFacility
Indicates that one facility is related to another as a sibling facility, typically sharing a common parent organization or similar hierarchical level.
-
E.
operatedFacilityNear
Indicates that an entity operated a facility located in close geographic proximity to another specified entity or place.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293430524819087984a699d1d3687 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.