Triple
T2039017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koltsevaya Line |
E44698
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Kiyevskaya |
E51121
|
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: Kiyevskaya | Statement: [Koltsevaya Line, hasStation, Kiyevskaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kiyevskaya Context triple: [Koltsevaya Line, hasStation, Kiyevskaya]
-
A.
Kievskaya
chosen
Kievskaya is a prominent Moscow Metro station complex known for its ornate, Ukrainian-themed architecture and role as a major transfer hub.
-
B.
Kakhovskaya
Kakhovskaya is a Moscow Metro station that serves as part of the city’s Big Circle Line.
-
C.
Kalinin
Kalinin is the former Soviet-era name of the Russian city now known as Tver, reflecting its renaming in honor of Bolshevik leader Mikhail Kalinin.
-
D.
Khoroshevskaya
Khoroshevskaya is a Moscow Metro station located on the Big Circle Line, serving the Khoroshyovsky District of the city.
-
E.
Novoslobodskaya
Novoslobodskaya is a Moscow Metro station famed for its distinctive stained-glass panels and ornate, cathedral-like interior design.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb951870481909dbdd8fc8b0c02fe |
completed | March 7, 2026, 5:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71a7e3408190955aa7f2534316dc |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:39 p.m.