Triple
T31675177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Хорошёвская |
E808379
|
entity |
| Predicate | принадлежитКольцевойЛинии |
P17559
|
FINISHED |
| Object | Большая кольцевая линия |
—
|
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: Большая кольцевая линия | Statement: [Хорошёвская, принадлежитКольцевойЛинии, Большая кольцевая линия]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: принадлежитКольцевойЛинии Context triple: [Хорошёвская, принадлежитКольцевойЛинии, Большая кольцевая линия]
-
A.
isOnOldestSectionOfMoscowMetro
Indicates that something is located on the oldest constructed section of the Moscow Metro network.
-
B.
hasAdjacentStationOnKoltsevayaLine
Indicates that one station is directly next to another station on the Koltsevaya (circle) metro line.
-
C.
isFirstMetroLineInCity
Indicates that a metro line is the earliest or original metro line established in a given city.
-
D.
соединяетЧерезНеву
Indicates that one entity connects or links another entity by means of or across the Neva River.
-
E.
hasMetroLine
chosen
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:02 p.m.