Triple
T5336464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Västerhaninge station |
E123837
|
entity |
| Predicate | hasPassengerSubwayOrFootbridge |
P25561
|
FINISHED |
| Object | footbridge |
—
|
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: footbridge | Statement: [Västerhaninge station, hasPassengerSubwayOrFootbridge, footbridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerSubwayOrFootbridge Context triple: [Västerhaninge station, hasPassengerSubwayOrFootbridge, footbridge]
-
A.
hasFootbridge
chosen
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
-
B.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
C.
hasSubway
Indicates that a place is served by or contains a subway (metro) system.
-
D.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
-
E.
hasUnderpass
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85b104c081908b81236a0142e1c8 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.