Triple
T3532334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Party of Regions |
E74687
|
entity |
| Predicate | timeAsRulingParty |
P41567
|
FINISHED |
| Object | 2010–2014 |
—
|
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: 2010–2014 | Statement: [Party of Regions, timeAsRulingParty, 2010–2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAsRulingParty Context triple: [Party of Regions, timeAsRulingParty, 2010–2014]
-
A.
endTimeAsRulingParty
Indicates the point in time at which an entity ceases to hold power or status as the ruling party.
-
B.
startTimeAsRulingParty
Indicates the point in time when an entity begins its tenure or role as the ruling party.
-
C.
endedYearsOfPartyControl
Indicates that an event or action resulted in the termination of a political party’s continuous control over a governing body or jurisdiction.
-
D.
yearsActiveInPolitics
chosen
Indicates the span of time during which an entity has been actively involved in political roles, activities, or office.
-
E.
historicalDominantParties
Indicates that certain political parties have historically held dominant or ruling positions within a given political system or jurisdiction.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9a14c881908932b17ed3eececb |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.