Triple
T635747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh |
E16616
|
entity |
| Predicate | twinCity |
P1072
|
FINISHED |
| Object | Kiev |
E17733
|
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: Kiev | Statement: [Edinburgh, twinCity, Kiev]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kiev Context triple: [Edinburgh, twinCity, Kiev]
-
A.
Kyiv
chosen
Kyiv is the capital and largest city of Ukraine, serving as its political, cultural, and economic center.
-
B.
Kharkiv
Kharkiv is Ukraine’s second-largest city and a major industrial, cultural, and educational center in the northeast of the country.
-
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.
Odesa
Odesa is a major port city on the Black Sea in southern Ukraine, known for its historic architecture, multicultural heritage, and key economic and cultural role in the country.
-
E.
Kryvyi Rih
Kryvyi Rih is a major industrial city in central Ukraine known for its extensive iron ore mining and steel production.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee667f08190a0332b8f6c569e1a |
completed | March 1, 2026, 8:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a58035296481908c177e782137b194 |
completed | March 2, 2026, 12:19 p.m. |
Created at: March 1, 2026, 7:35 p.m.