Triple
T29717033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cámara de Senadores |
E751939
|
entity |
| Predicate | eligePor |
P381
|
FINISHED |
| Object | sufragio universal directo |
—
|
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: sufragio universal directo | Statement: [Cámara de Senadores, eligePor, sufragio universal directo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligePor Context triple: [Cámara de Senadores, eligePor, sufragio universal directo]
-
A.
madeChoiceBetween
Indicates that an entity selected one option from among two or more specified alternatives.
-
B.
selectionRitual
Indicates a process or ceremony through which one or more entities are chosen from a set of candidates.
-
C.
selectionMadeBy
chosen
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
D.
decisionMakingTool
Indicates that an entity functions as a tool or system used to support, structure, or carry out decision-making processes for another entity.
-
E.
selectionFrom
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672dd9ab881908969657a9bd48098 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:34 p.m.