Triple
T31527757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Avenue (Minsk) |
E804390
|
entity |
| Predicate | hasMetroStationsAlong |
P39430
|
FINISHED |
| Object | Ploshcha Lenina metro station |
—
|
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: Ploshcha Lenina metro station | Statement: [Independence Avenue (Minsk), hasMetroStationsAlong, Ploshcha Lenina metro station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetroStationsAlong Context triple: [Independence Avenue (Minsk), hasMetroStationsAlong, Ploshcha Lenina metro station]
-
A.
hasMetroStations
chosen
Indicates that a place or area is served by one or more metro (subway) stations.
-
B.
hasMetroTerminus
Indicates that one location serves as the terminal (end) station of a metro line for another location.
-
C.
hasMetroLine
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
D.
hasMetroStationOnBridge
Indicates that a metro station is located on or integrated into a bridge.
-
E.
hasMBTACommuterRailTerminus
Indicates that one entity serves as the endpoint or final stop of an MBTA Commuter Rail line for the other entity.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 30, 2026, 9:59 p.m.