Triple
T12838730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumy Oblast |
E306986
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Lebedyn |
E1004144
|
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: Lebedyn | Statement: [Sumy Oblast, containsCity, Lebedyn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lebedyn Context triple: [Sumy Oblast, containsCity, Lebedyn]
-
A.
Lebedyn
chosen
Lebedyn is a city in northeastern Ukraine known for its historical architecture and role as a local cultural and administrative center.
-
B.
Lebedus
Lebedus was an ancient Greek city of Ionia on the western coast of Asia Minor, known as a minor but strategically located coastal settlement involved in regional trade and politics.
-
C.
Barysaw
Barysaw is a city in Belarus known as an important industrial and transportation center northeast of Minsk.
-
D.
Zvenyhorodka
Zvenyhorodka is a town in central Ukraine that serves as a local administrative and cultural center within Cherkasy Oblast.
-
E.
Bogrod
Bogrod is a goblin banker who works at Gringotts Wizarding Bank in the Harry Potter series.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff11b4481909fb2f92c46186853 |
completed | April 10, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b9dc1e48190993430956e0fcfdc |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:35 p.m.