Triple
T4465614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyiv Metro |
E98369
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Dnipro |
E38828
|
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: Dnipro | Statement: [Kyiv Metro, hasStation, Dnipro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dnipro Context triple: [Kyiv Metro, hasStation, Dnipro]
-
A.
Dnipro
chosen
Dnipro is one of Ukraine’s largest industrial and cultural centers, located on the Dnieper River in the central-eastern part of the country.
-
B.
Kryvyi Rih
Kryvyi Rih is a major industrial city in central Ukraine known for its extensive iron ore mining and steel production.
-
C.
Kremenchuk
Kremenchuk is an industrial city in central Ukraine on the Dnieper River, historically significant as a major transport and strategic hub.
-
D.
Kharkiv
Kharkiv is Ukraine’s second-largest city and a major industrial, cultural, and educational center in the northeast of the country.
-
E.
Dniprodzerzhynsk
Dniprodzerzhynsk (now officially called Kamianske) is an industrial city in central Ukraine known for its heavy industry and metallurgical enterprises along the Dnieper River.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356991a588190be2f95fd957d7f99 |
completed | March 13, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69befe41822c8190b406c192170af3d1 |
completed | March 21, 2026, 8:23 p.m. |
Created at: March 12, 2026, 11:34 p.m.