Triple
T16385555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Олександр Турчинов |
E397912
|
entity |
| Predicate | початокТермінуЯкПершийВіцеПремʼєр |
P123199
|
FINISHED |
| Object | 2007-12-18 |
—
|
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: 2007-12-18 | Statement: [Олександр Турчинов, початокТермінуЯкПершийВіцеПремʼєр, 2007-12-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: початокТермінуЯкПершийВіцеПремʼєр Context triple: [Олександр Турчинов, початокТермінуЯкПершийВіцеПремʼєр, 2007-12-18]
-
A.
firstTermStart
Indicates that an entity marks the starting point or initial term in an ordered sequence, period, or agreement.
-
B.
officeEndTime (Prime Minister, first term)
Indicates the time at which the Prime Minister’s first term in office officially ended.
-
C.
primeMinisterTermStart
Indicates the date on which an individual officially begins serving as prime minister.
-
D.
endTimeFirstTermAsPrimeMinister
Indicates the date and time when an individual’s first term serving as prime minister comes to an end.
-
E.
firstOfficeHolderStart
Indicates the date or time when the first person to hold a particular office or position began their term.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263c60088190b85a8c02bc3ef315 |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.