Triple
T1737565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volyn Oblast |
E37952
|
entity |
| Predicate | headOfExecutive |
P452
|
FINISHED |
| Object | Governor of Volyn Oblast |
—
|
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: Governor of Volyn Oblast | Statement: [Volyn Oblast, headOfExecutive, Governor of Volyn Oblast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfExecutive Context triple: [Volyn Oblast, headOfExecutive, Governor of Volyn Oblast]
-
A.
headOfOffice
Indicates that one entity serves as the chief or leading authority in charge of a particular office or organizational unit.
-
B.
headOfGovernmentBody
chosen
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
-
C.
headOfGovernment
Indicates that one entity serves as the chief executive authority or leader of the government of another entity.
-
D.
headOfGovernmentForOffice
Indicates that a person serves as the head of government corresponding to a specific governmental office or position.
-
E.
headOfRepublic
Indicates the relationship in which a person holds the highest office and serves as the chief of state of a republic.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.