Triple
T37131585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kievskaya (Koltsevaya line) |
E919530
|
entity |
| Predicate | hasCircularLineRole |
P111452
|
FINISHED |
| Object | interchange on Koltsevaya line |
—
|
LITERAL 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: interchange on Koltsevaya line | Statement: [Kievskaya (Koltsevaya line), hasCircularLineRole, interchange on Koltsevaya line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCircularLineRole Context triple: [Kievskaya (Koltsevaya line), hasCircularLineRole, interchange on Koltsevaya line]
-
A.
hasCircularLineFunction
Indicates that an entity possesses or is associated with a function that operates in a circular or looped manner.
-
B.
hasLineRole
Indicates that an entity participates in a line (such as a queue, route, or sequence) with a specific functional role or position within that line.
-
C.
hasLoopRole
chosen
Indicates that an entity participates in a loop structure with a specific functional role within that loop.
-
D.
hasCircularOperation
Indicates that an entity performs or supports an operation whose process or flow follows a circular or repeating cycle.
-
E.
hasCircularWalk
Indicates that an entity possesses or includes a walking path or route that forms a closed circular loop.
- F. None of above.
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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:15 p.m.