Triple
T7559294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gobernador de Cundinamarca |
E178752
|
entity |
| Predicate | esElegidoPor |
P122
|
FINISHED |
| Object | voto popular |
—
|
LITERAL FINISHED |
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: voto popular | Statement: [Gobernador de Cundinamarca, esElegidoPor, voto popular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esElegidoPor Context triple: [Gobernador de Cundinamarca, esElegidoPor, voto popular]
-
A.
electedWith
Indicates that one entity attained an elected position or office together with, or as part of the same electoral outcome as, another entity.
-
B.
elects
chosen
Indicates that one entity selects or chooses another entity for a position, role, or office, typically through a formal voting process.
-
C.
electedWithin
Indicates that one entity was chosen or appointed to a position, office, or role within the jurisdiction, boundaries, or organizational scope of another entity.
-
D.
electedFrom
Indicates that an individual has been chosen through an election to represent or serve a specific geographic area, constituency, or jurisdiction.
-
E.
isUsuallyElectedFor
Indicates that an entity typically attains a position, role, or office through an election process.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8dc7d288190a0d08ba704cc3fc2 |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.