Triple
T14904372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevertire |
E360088
|
entity |
| Predicate | directionFromNyngan |
P116608
|
FINISHED |
| Object | south-east |
—
|
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-east | Statement: [Nevertire, directionFromNyngan, south-east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromNyngan Context triple: [Nevertire, directionFromNyngan, south-east]
-
A.
directionFromCairns
Indicates the spatial direction or bearing of one location or object as measured outward from Cairns.
-
B.
directionRelativeToEmeraldCity
Indicates the compass direction or positional bearing of one place or object relative to the location of Emerald City.
-
C.
directionFromAliceSprings
Indicates the cardinal or relative compass direction of an entity as measured from Alice Springs toward that entity.
-
D.
directionFromRyde
Indicates the compass direction or relative bearing of one location or object measured from the reference point Ryde.
-
E.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60cd5588190b1efecc2b220da69 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:12 a.m.