Triple
T15654620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tharwa |
E376398
|
entity |
| Predicate | directionFromCanberraCBD |
P119618
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Tharwa, directionFromCanberraCBD, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromCanberraCBD Context triple: [Tharwa, directionFromCanberraCBD, south]
-
A.
directionFromCanberra
Indicates the cardinal or relative compass direction in which one location lies when measured from Canberra.
-
B.
directionFromBrisbaneCBD
Indicates the compass direction or relative bearing of a place or object when measured outward from the Brisbane Central Business District.
-
C.
directionFromAdelaideCBD
Indicates the compass direction or bearing of an entity’s location relative to the Adelaide Central Business District.
-
D.
directionFromWollongongCBD
Indicates the compass direction in which one location lies relative to the Wollongong Central Business District (CBD).
-
E.
directionFromSydney
Indicates the compass direction or relative bearing of one location when measured outward starting from Sydney.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef089948190902ec22f4d7bc932 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.