Triple
T14686221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBD and South East Light Rail |
E344913
|
entity |
| Predicate | endStationOfL3 |
P15150
|
FINISHED |
| Object | Juniors Kingsford |
—
|
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: Juniors Kingsford | Statement: [CBD and South East Light Rail, endStationOfL3, Juniors Kingsford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endStationOfL3 Context triple: [CBD and South East Light Rail, endStationOfL3, Juniors Kingsford]
-
A.
endLocationOfJourney
Indicates the final destination or stopping point reached at the conclusion of a journey or trip.
-
B.
railwayUpperTerminus
Indicates that a railway line or route reaches its upper (typically higher-altitude or upstream) terminal endpoint at the related location.
-
C.
endStationProvidesAccessTo
Indicates that a particular end station offers access or connectivity to another location, service, or network resource.
-
D.
thirdStation
Indicates that one entity is the third station in an ordered sequence or route relative to another entity.
-
E.
terminusStation
chosen
Indicates that a station serves as the final endpoint or terminal stop for a given route 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58306548190b981956a83a84b95 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.