Triple
T25386549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burwood railway station |
E631539
|
entity |
| Predicate | isOnSuburbanLine |
P158254
|
FINISHED |
| Object | Alamein line |
—
|
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: Alamein line | Statement: [Burwood railway station, isOnSuburbanLine, Alamein line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnSuburbanLine Context triple: [Burwood railway station, isOnSuburbanLine, Alamein line]
-
A.
isSuburbanRailIn
Indicates that a suburban rail service or line operates within or belongs to a specified geographic area or region.
-
B.
isOnAutomatedMetroLine
Indicates that something (typically a metro station, segment, or service) belongs to or operates on a metro line that runs with automated (driverless or semi-driverless) train control.
-
C.
hasMetroLine
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
D.
isSuburbanStationFor
Indicates that a station primarily serves a suburban area or functions as a transit hub for suburban commuters relative to a larger urban center.
-
E.
hasSubway
Indicates that a place is served by or contains a subway (metro) system.
- F. None of above. chosen
Provenance (4 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5656a1e8081908dbec5e5e1d21319 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:47 p.m.