Triple
T10860929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolomenskaya |
E256399
|
entity |
| Predicate | isNorthOf |
P305
|
FINISHED |
| Object | Kashirskaya station |
E794191
|
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: Kashirskaya station | Statement: [Kolomenskaya, isNorthOf, Kashirskaya station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kashirskaya station Context triple: [Kolomenskaya, isNorthOf, Kashirskaya station]
-
A.
Kashirskaya station
chosen
Kashirskaya station is a major Moscow Metro interchange station located in the southern part of Moscow, serving as a junction between multiple lines.
-
B.
Krasnoselskaya station
Krasnoselskaya station is a Moscow Metro station known for its early Soviet-era architecture and location on the system’s first metro line.
-
C.
Kachinskaya station
Kachinskaya station is a stop on the Volgograd Metrotram light rail system in Volgograd, Russia.
-
D.
Taganskaya station
Taganskaya station is a Moscow Metro station known for its distinctive post-war Stalinist architecture and role as a key interchange hub in the city’s subway network.
-
E.
Timiryazevskaya station
Timiryazevskaya station is a Moscow Metro station that serves as a key stop and namesake on the Serpukhovsko–Timiryazevskaya Line.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7515186f08190a5cc388a7d936c4f |
completed | April 9, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e54263e930819099524917506c7eab |
completed | April 19, 2026, 9 p.m. |
Created at: April 8, 2026, 9:20 p.m.