Triple
T27200144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilydale railway station |
E683712
|
entity |
| Predicate | hasTerminatingTrains |
P99236
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lilydale railway station, hasTerminatingTrains, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminatingTrains Context triple: [Lilydale railway station, hasTerminatingTrains, yes]
-
A.
isTerminalForSomeTrains
chosen
Indicates that a station or stop serves as the final destination (terminus) for at least one train route.
-
B.
trainsOn
Indicates that one entity receives training, instruction, or practice using or based on another entity (such as a resource, dataset, tool, or subject).
-
C.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
D.
hasTerminatingPlatforms
Indicates that the subject location or facility includes platforms where rail or transit services begin or end their routes, rather than passing through.
-
E.
hasNextTrainIndicators
Indicates that there are one or more indicators providing information about the next train in a sequence or schedule.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 9:36 a.m.