Triple
T17709756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sviatoshynsko–Brovarska line |
E441531
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Sviatoshyn |
—
|
NE NERFINISHED |
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: Sviatoshyn | Statement: [Sviatoshynsko–Brovarska line, hasStation, Sviatoshyn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sviatoshyn Context triple: [Sviatoshynsko–Brovarska line, hasStation, Sviatoshyn]
-
A.
Sviatoshyn
chosen
Sviatoshyn is a residential neighborhood in Kyiv, Ukraine, known for its location along the city’s metro system and its mix of Soviet-era housing and green spaces.
-
B.
Usvyaty
Usvyaty is an urban-type settlement in Pskov Oblast, Russia, known as a local administrative and cultural center near the borders with Belarus and Latvia.
-
C.
Mohyliv-Podilskyi
Mohyliv-Podilskyi is a city in western Ukraine situated on the Dniester River near the border with Moldova.
-
D.
Horokhiv
Horokhiv is a small town in western Ukraine known for its location within the historic Volyn region.
-
E.
Letychiv
Letychiv is an urban-type settlement in western Ukraine known for its historic fortress and role as a local administrative center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729a9a9c81908d65ff0bda12c961 |
completed | April 19, 2026, 6:13 a.m. |
Created at: April 10, 2026, 10:05 a.m.