Triple
T14307357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minto railway station |
E354731
|
entity |
| Predicate | hasPedestrianOverbridge |
P60843
|
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: [Minto railway station, hasPedestrianOverbridge, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianOverbridge Context triple: [Minto railway station, hasPedestrianOverbridge, yes]
-
A.
hasFootbridge
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
-
B.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
C.
hasPedestrianOverpass
chosen
Indicates that there exists a pedestrian overpass connecting or spanning parts of the referenced location or infrastructure.
-
D.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
E.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b156b0819083f2bd319deed1b6 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.