Triple
T16908688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSPU |
E424633
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kryvyi Rih |
E17094
|
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: Kryvyi Rih | Statement: [KSPU, locatedIn, Kryvyi Rih]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kryvyi Rih Context triple: [KSPU, locatedIn, Kryvyi Rih]
-
A.
Kryvyi Rih
chosen
Kryvyi Rih is a major industrial city in central Ukraine known for its extensive iron ore mining and steel production.
-
B.
Mykolaiv
Mykolaiv is a major shipbuilding and industrial city in southern Ukraine located near the Black Sea.
-
C.
Dnipro
Dnipro is one of Ukraine’s largest industrial and cultural centers, located on the Dnieper River in the central-eastern part of the country.
-
D.
Kherson
Kherson is a port city in southern Ukraine near the Black Sea, historically significant as a shipbuilding and industrial center and strategically important due to its location on the Dnieper River.
-
E.
Chornomorske
Chornomorske is a coastal settlement in western Crimea known for its location on the Black Sea and its role as a local resort and fishing community.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3ca3b1ad081908a032bff9699f2fe |
completed | April 18, 2026, 6:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180c181b08190a6e8912f4e1da6a0 |
completed | May 11, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:30 a.m.