Triple
T33223688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnoselskaya |
E850491
|
entity |
| Predicate | isOnOldestMetroLineInMoscow |
P106059
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Krasnoselskaya, isOnOldestMetroLineInMoscow, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnOldestMetroLineInMoscow Context triple: [Krasnoselskaya, isOnOldestMetroLineInMoscow, yes]
-
A.
isOnOldestSectionOfMoscowMetro
chosen
Indicates that something is located on the oldest constructed section of the Moscow Metro network.
-
B.
isFirstMetroLineInCity
Indicates that a metro line is the earliest or original metro line established in a given city.
-
C.
isPartOfOneOfOldestMetroLinesInContinentalEurope
Indicates that something belongs to one of the earliest-established metro (subway) lines located in continental Europe.
-
D.
isAmongOldestUndergroundSystemsIn
Indicates that an underground transportation system ranks among the oldest of its kind within a specified location or region.
-
E.
oldestSubwayLineIn
Indicates that a subway line is the earliest-built or longest-operating subway line within a specified geographic area or transit system.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.