Triple
T28751780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teralba |
E731548
|
entity |
| Predicate | directionToNewcastleCBD |
P182838
|
FINISHED |
| Object | southwest |
—
|
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: southwest | Statement: [Teralba, directionToNewcastleCBD, southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionToNewcastleCBD Context triple: [Teralba, directionToNewcastleCBD, southwest]
-
A.
directionFromNewcastle
Indicates the compass direction or relative bearing of one place or object when measured starting from Newcastle as the reference point.
-
B.
distanceFromNewcastleCBD_km
Indicates the physical distance, measured in kilometers, between an entity and the central business district (CBD) of Newcastle.
-
C.
directionFromCanberraCBD
Indicates the compass direction in which one location lies relative to the Canberra Central Business District (CBD).
-
D.
directionFromWollongongCBD
Indicates the compass direction in which one location lies relative to the Wollongong Central Business District (CBD).
-
E.
distanceFromNewcastle
Indicates the spatial distance between a given entity or location and the city of Newcastle.
- F. None of above. chosen
Provenance (4 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: April 28, 2026, 6:07 a.m.