Triple
T26326613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torneo Internacional del Joropo |
E662268
|
entity |
| Predicate | mainStageCity |
P3207
|
FINISHED |
| Object | Villavicencio |
—
|
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: Villavicencio | Statement: [Torneo Internacional del Joropo, mainStageCity, Villavicencio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStageCity Context triple: [Torneo Internacional del Joropo, mainStageCity, Villavicencio]
-
A.
cityCenterStage
Indicates that an event, activity, or focus is taking place prominently in the central area of a city.
-
B.
isMainStageOf
Indicates that one entity serves as the primary or central stage or platform on which the other entity occurs, is presented, or is featured.
-
C.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
D.
city2
chosen
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
-
E.
cityOn
Indicates that a city is geographically located on a specified landform, area, or administrative region.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 10:31 p.m.