Triple
T1557585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploshchad Vosstaniya metro station |
E33242
|
entity |
| Predicate | isMajorStation |
P14730
|
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: [Ploshchad Vosstaniya metro station, isMajorStation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorStation Context triple: [Ploshchad Vosstaniya metro station, isMajorStation, yes]
-
A.
hasMajorRailwayStation
Indicates that a place contains or is served by a principal railway station that functions as a major hub for rail transport.
-
B.
isMajorInterchangeFor
Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
-
C.
isBusiestStationIn
Indicates that a station has the highest level of activity (e.g., passenger or traffic volume) within a specified area or system.
-
D.
isMajor
chosen
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
E.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
- 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.