Triple
T26240962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide–Melbourne railway |
E656310
|
entity |
| Predicate | terminusStationMelbourne |
P15150
|
FINISHED |
| Object | Southern Cross 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: Southern Cross railway station | Statement: [Adelaide–Melbourne railway, terminusStationMelbourne, Southern Cross railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusStationMelbourne Context triple: [Adelaide–Melbourne railway, terminusStationMelbourne, Southern Cross railway station]
-
A.
terminusStation
chosen
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
B.
terminalStationSouth
Indicates that a given station serves as the southern terminal (end point) of a particular route or line.
-
C.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
D.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
E.
railTerminusFor
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 9:03 p.m.