Triple
T6825787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institutional Revolutionary Party |
E157011
|
entity |
| Predicate | heldOfficeContinuously |
P73270
|
FINISHED |
| Object | 1929–2000 |
—
|
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: 1929–2000 | Statement: [Institutional Revolutionary Party, heldOfficeContinuously, 1929–2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldOfficeContinuously Context triple: [Institutional Revolutionary Party, heldOfficeContinuously, 1929–2000]
-
A.
heldPoliticalOfficeIn
Indicates that an entity served in a political office or position within a specified governmental body or jurisdiction.
-
B.
remainedInForceUntil
Indicates that a rule, condition, or state continued to be valid or effective up to a specified point in time.
-
C.
succeededInOffice
Indicates that one officeholder directly followed another in holding the same official position.
-
D.
allowsContinuationOfOffice
Indicates that one entity grants or enables another entity to continue holding or exercising a particular office or position beyond its current term or conditions.
-
E.
termInOffice
Indicates the period during which an individual officially holds a particular office or position.
- F. None of above. chosen
Provenance (4 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d58375248190935dd38d618994e3 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:18 p.m.