Triple
T16385564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Олександр Турчинов |
E397912
|
entity |
| Predicate | рольУПодіях |
P4073
|
FINISHED |
| Object | один з керівників опозиції під час Євромайдану |
—
|
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: один з керівників опозиції під час Євромайдану | Statement: [Олександр Турчинов, рольУПодіях, один з керівників опозиції під час Євромайдану]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: рольУПодіях Context triple: [Олександр Турчинов, рольУПодіях, один з керівників опозиції під час Євромайдану]
-
A.
significantEventRole
Indicates that an entity plays an important or defining role in a particular significant event.
-
B.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
C.
eventoDesencadenante
Indicates that one event serves as the trigger or initiating cause for another event or process.
-
D.
roleInReact
Indicates that an entity participates in a reaction with a specified functional or contextual role (e.g., reactant, product, catalyst, or regulator).
-
E.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
- 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_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. |
Created at: April 10, 2026, 5:08 a.m.