Triple
T2490803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novoslobodskaya |
E52035
|
entity |
| Predicate | line |
P1293
|
FINISHED |
| Object | Koltsevaya line |
E44698
|
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: Koltsevaya line | Statement: [Novoslobodskaya, line, Koltsevaya line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koltsevaya line Context triple: [Novoslobodskaya, line, Koltsevaya line]
-
A.
Koltsevaya Line
chosen
The Koltsevaya Line is the circular line of the Moscow Metro, known for encircling the city center and connecting many of the system’s radial lines.
-
B.
Filevskaya Line
Filevskaya Line is one of the lines of the Moscow Metro, known for its partially surface-level sections and service to western districts of the city.
-
C.
Butovskaya Line
The Butovskaya Line is a light metro line in the Moscow Metro system serving the Butovo district in the city’s south.
-
D.
Zhdanovskaya Line
Zhdanovskaya Line was the former name of a line of the Moscow Metro, later known as the Tagansko–Krasnopresnenskaya Line.
-
E.
Sokolnicheskaya Line
The Sokolnicheskaya Line is one of the oldest and most important lines of the Moscow Metro, running generally north–south and serving several central and historic districts of the city.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd18fe32081909580c6272a6013c5 |
completed | March 7, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af8383c0988190885a865c3150c64d |
completed | March 10, 2026, 2:35 a.m. |
Created at: March 6, 2026, 9:45 p.m.