Triple
T26240961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide–Melbourne railway |
E656310
|
entity |
| Predicate | terminusStationAdelaide |
P15150
|
FINISHED |
| Object | Adelaide Parklands Terminal |
—
|
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: Adelaide Parklands Terminal | Statement: [Adelaide–Melbourne railway, terminusStationAdelaide, Adelaide Parklands Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusStationAdelaide Context triple: [Adelaide–Melbourne railway, terminusStationAdelaide, Adelaide Parklands Terminal]
-
A.
terminalStationSouth
Indicates that a given station serves as the southern terminal (end point) of a particular route or line.
-
B.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
-
C.
terminusStation
chosen
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
D.
terminusCitySoutheast
Indicates that something serves as the southeastern terminus or endpoint of a route, line, or connection in a particular city.
-
E.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 9:03 p.m.