Triple
T26119362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebden |
E658914
|
entity |
| Predicate | locatedInDirectionFromWodonga |
P193106
|
FINISHED |
| Object | 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: east | Statement: [Ebden, locatedInDirectionFromWodonga, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromWodonga Context triple: [Ebden, locatedInDirectionFromWodonga, east]
-
A.
directionToWodonga
Indicates the directional relationship pointing from a given location or entity toward Wodonga.
-
B.
distanceFromWangaratta
Indicates the measured distance between a given location and the town of Wangaratta.
-
C.
directionFromShepparton
Indicates the spatial direction or bearing of one location as measured outward from Shepparton.
-
D.
directionFromGoulburn
Indicates the compass direction or relative bearing of one location when measured from Goulburn.
-
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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 26, 2026, 8:07 p.m.