Triple
T8411276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petro Doroshenko |
E198628
|
entity |
| Predicate | burialPlace |
P196
|
FINISHED |
| Object | Yaropolch |
E731516
|
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: Yaropolch | Statement: [Petro Doroshenko, burialPlace, Yaropolch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yaropolch Context triple: [Petro Doroshenko, burialPlace, Yaropolch]
-
A.
Yaropolch
chosen
Yaropolch is a village in Russia historically noted as the place where Ukrainian Hetman Petro Doroshenko died.
-
B.
Ivanychi
Ivanychi is a small urban-type settlement in western Ukraine that serves as a local administrative and community center within Volyn Oblast.
-
C.
Khovrino
Khovrino is a Moscow Metro station serving as the northern terminus of the Zamoskvoretskaya Line.
-
D.
Zolotonosha
Zolotonosha is a historic town in central Ukraine, located in the Cherkasy region on the banks of the Zolotonoshka River.
-
E.
Zhmerynka
Zhmerynka is a city in central Ukraine known as an important regional railway junction and administrative center.
- 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_69ce1d3d9f848190bd425b80aa58a376 |
completed | April 2, 2026, 7:39 a.m. |
Created at: March 30, 2026, 6:05 p.m.