Triple
T33645904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voivode of Kiev |
E861959
|
entity |
| Predicate | positionHeldInTerritory |
P126851
|
FINISHED |
| Object | Kiev |
—
|
NE NERFINISHED |
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: Kiev | Statement: [Voivode of Kiev, positionHeldInTerritory, Kiev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionHeldInTerritory Context triple: [Voivode of Kiev, positionHeldInTerritory, Kiev]
-
A.
heldTerritory
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
B.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
C.
positionHeldInJurisdiction
chosen
Indicates that an entity holds or has held a specific position, office, or role within a particular legal or geographic jurisdiction.
-
D.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
E.
positionHeldUnder
Indicates that one entity holds or held a specific position, office, or role under the authority, administration, or jurisdiction of another entity.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:42 a.m.