Triple
T25208174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Loop group of stations |
E631309
|
entity |
| Predicate | hasAboveGroundStation |
P106588
|
FINISHED |
| Object | Flinders Street railway 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: Flinders Street railway station | Statement: [City Loop group of stations, hasAboveGroundStation, Flinders Street railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAboveGroundStation Context triple: [City Loop group of stations, hasAboveGroundStation, Flinders Street railway station]
-
A.
locatedAboveGround
Indicates that one entity is positioned at a level higher than the ground surface, not buried or below ground.
-
B.
hasStationNear
Indicates that one entity has a station located in close proximity to another entity.
-
C.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
D.
hasAltitudeStation
Indicates that something is associated with or located at a station characterized by a specific altitude.
-
E.
isSurfaceStation
chosen
Indicates that the station is located at or on the surface (e.g., ground level) rather than being underground, elevated, or otherwise non-surface.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474bda9288190947d325fe514571d |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:52 p.m.