Triple
T14620610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guide Falls (near Burnie) |
E343208
|
entity |
| Predicate | directionFromBurnie |
P115082
|
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: [Guide Falls (near Burnie), directionFromBurnie, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromBurnie Context triple: [Guide Falls (near Burnie), directionFromBurnie, south]
-
A.
directionFromCoffsHarbour
Indicates the compass direction or bearing of one location as measured from Coffs Harbour.
-
B.
directionFromBrisbane
Indicates the cardinal or relative compass direction of an entity’s location measured from Brisbane.
-
C.
directionFromHobart
Indicates the cardinal or relative direction in which one entity is located from Hobart.
-
D.
directionFromAdelaide
Indicates the directional relationship of one location as measured outward from Adelaide as the point of reference.
-
E.
directionFromMelbourne
Indicates the compass direction in which one entity is located relative to Melbourne.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb466a61c81908a110d40fb959b6f |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.