Triple
T34839132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port MacDonnell |
E1004284
|
entity |
| Predicate | directionFromMountGambier |
P195511
|
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: [Port MacDonnell, directionFromMountGambier, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromMountGambier Context triple: [Port MacDonnell, directionFromMountGambier, south]
-
A.
directionFromAdelaide
Indicates the directional relationship of one location as measured outward from Adelaide as the point of reference.
-
B.
directionFromGoulburn
Indicates the compass direction or relative bearing of one location when measured from Goulburn.
-
C.
directionFromHobart
Indicates the cardinal or relative direction in which one entity is located from Hobart.
-
D.
directionFromBurnie
Indicates the compass direction in which one entity or location lies relative to Burnie.
-
E.
directionFromCoffsHarbour
Indicates the compass direction or bearing of one location as measured from Coffs Harbour.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4 p.m.