Triple
T14862527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niagara Park railway station |
E349531
|
entity |
| Predicate | directionFromSydneyCentral |
P34513
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Niagara Park railway station, directionFromSydneyCentral, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromSydneyCentral Context triple: [Niagara Park railway station, directionFromSydneyCentral, north]
-
A.
directionFromSydney
chosen
Indicates the compass direction or relative bearing of one location when measured outward starting from Sydney.
-
B.
directionFromCanberra
Indicates the cardinal or relative compass direction in which one location lies when measured from Canberra.
-
C.
directionFromMelbourne
Indicates the compass direction in which one entity is located relative to Melbourne.
-
D.
directionFromCoffsHarbour
Indicates the compass direction or bearing of one location as measured from Coffs Harbour.
-
E.
directionFromBrisbaneCBD
Indicates the compass direction or relative bearing of a place or object when measured outward from the Brisbane Central Business District.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded573cba881908d6d9ac570a64e5f |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.