Triple
T25147529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Box Hill railway station |
E629975
|
entity |
| Predicate | formerTerminusOfLine |
P28772
|
FINISHED |
| Object | Lilydale 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: Lilydale line | Statement: [Box Hill railway station, formerTerminusOfLine, Lilydale line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTerminusOfLine Context triple: [Box Hill railway station, formerTerminusOfLine, Lilydale line]
-
A.
formerTerminusFor
chosen
Indicates that a location once served as the endpoint or final stop of a route, line, or service, but no longer holds that status.
-
B.
formerLineName
Indicates that the object is a previous or former name by which the referenced line was known.
-
C.
formerTerminalStation
Indicates that a location once served as the end point (terminus) of a transportation line or route but no longer holds that status.
-
D.
lineTerminusDirection
Indicates the directional orientation or bearing at which a line segment or route terminates at its endpoint.
-
E.
formerLine
Indicates that an entity previously served as a particular transit or service line but no longer does so.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 18, 2026, 6:30 a.m.