Triple
T25730429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakleigh railway station |
E645223
|
entity |
| Predicate | hasOverpassOrSubway |
P158586
|
FINISHED |
| Object | pedestrian subway |
—
|
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: pedestrian subway | Statement: [Oakleigh railway station, hasOverpassOrSubway, pedestrian subway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOverpassOrSubway Context triple: [Oakleigh railway station, hasOverpassOrSubway, pedestrian subway]
-
A.
hasOverpassOrSubway
chosen
Indicates that one location is connected to or accessible from another via an overpass or a subway passage.
-
B.
hasSubway
Indicates that a place is served by or contains a subway (metro) system.
-
C.
hasSubwayComplex
Indicates that one entity contains or is associated with a subway complex as part of its structure or facilities.
-
D.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
-
E.
hasSubwaySymbol
Indicates that one entity is used as the official subway symbol or icon representing another 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcbb125481909d97550556700576 |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 11:12 p.m.