Triple
T29089237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambiemos |
E734209
|
entity |
| Predicate | successorNameUsed |
P155706
|
FINISHED |
| Object | Juntos por el Cambio |
—
|
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: Juntos por el Cambio | Statement: [Cambiemos, successorNameUsed, Juntos por el Cambio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorNameUsed Context triple: [Cambiemos, successorNameUsed, Juntos por el Cambio]
-
A.
successorNameInUseSince
Indicates that the successor’s name has been actively used starting from a specified point in time.
-
B.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
C.
hasOfficialSuccessorName
Indicates that an entity has an officially designated successor identified by a specific name.
-
D.
successorNameForm
chosen
Indicates that the object is the name or naming form used for the successor entity that follows the subject in a sequence or lineage.
-
E.
successorNameInService
Indicates that one entity is the name of the successor that takes over a role, position, or function within a particular service or service context.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 28, 2026, 11:03 a.m.