Triple
T1557550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploshchad Vosstaniya metro station |
E33242
|
entity |
| Predicate | metroLineNumber |
P1864
|
FINISHED |
| Object | Line 1 |
—
|
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: Line 1 | Statement: [Ploshchad Vosstaniya metro station, metroLineNumber, Line 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metroLineNumber Context triple: [Ploshchad Vosstaniya metro station, metroLineNumber, Line 1]
-
A.
terminalNumber
Indicates the specific terminal identifier associated with an entity, such as a device, port, or connection point, within a larger system or network.
-
B.
stationNumber
Indicates the specific station identifier or code assigned to an entity within a system or network.
-
C.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
D.
routeNumber
chosen
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
E.
lineName
Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:27 p.m.