Triple
T16196112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Brisbane railway station |
E393063
|
entity |
| Predicate | distanceFromCentralStation |
P69004
|
FINISHED |
| Object | about 1.6 kilometres |
—
|
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: about 1.6 kilometres | Statement: [South Brisbane railway station, distanceFromCentralStation, about 1.6 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCentralStation Context triple: [South Brisbane railway station, distanceFromCentralStation, about 1.6 kilometres]
-
A.
distanceFromStation
chosen
Indicates the measured spatial separation between an entity and a specified station.
-
B.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
C.
distanceToRailhead
Indicates the measured distance between a location or object and the nearest railhead (rail transport access point).
-
D.
distanceFromSouthStation
Indicates the measured distance between a given location or entity and South Station.
-
E.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d91130819080da4e2611612e27 |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.