Triple
T21882070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidente del Senado de la República |
E540311
|
entity |
| Predicate | esElegidoDeEntre |
P96636
|
FINISHED |
| Object | senadores de la República |
—
|
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: senadores de la República | Statement: [Presidente del Senado de la República, esElegidoDeEntre, senadores de la República]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esElegidoDeEntre Context triple: [Presidente del Senado de la República, esElegidoDeEntre, senadores de la República]
-
A.
symbolicallyChosenFor
Indicates that an entity has been selected to represent or stand in for something else in a symbolic or emblematic way.
-
B.
selectionRitual
chosen
Indicates a process or ceremony through which one or more entities are chosen from a set of candidates.
-
C.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
D.
madeChoiceBetween
Indicates that an entity selected one option from among two or more specified alternatives.
-
E.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e890088190aa3023c78a99a536 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:04 p.m.