Triple
T8411319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Mazepa |
E198629
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Baturyn |
E191041
|
NE 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: Baturyn | Statement: [Ivan Mazepa, residence, Baturyn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baturyn Context triple: [Ivan Mazepa, residence, Baturyn]
-
A.
Baturyn
chosen
Baturyn is a historic town in northern Ukraine that served as a major political and military center of the Cossack Hetmanate in the 17th–18th centuries.
-
B.
Makiyivka
Makiyivka is a major industrial city in eastern Ukraine’s Donetsk region, historically known for its coal mining and heavy industry.
-
C.
Kakhovskaya
Kakhovskaya is a Moscow Metro station that serves as part of the city’s Big Circle Line.
-
D.
Mukhavets
Mukhavets is a river in western Belarus that flows through the city of Brest before joining the Western Bug.
-
E.
Horlivka
Horlivka is an industrial city in eastern Ukraine’s Donetsk region, known for its coal mining and chemical industries and its location within the contested Donbas area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e0341c819080506e696131671e |
completed | March 31, 2026, 8:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecc3c0d508190bc0c7bd89f040967 |
completed | April 2, 2026, 8:06 p.m. |
Created at: March 30, 2026, 6:05 p.m.