Triple
T13501564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuross Head |
E320903
|
entity |
| Predicate | distanceToMoruya |
P110670
|
FINISHED |
| Object | approximately 20 kilometres 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: approximately 20 kilometres south | Statement: [Tuross Head, distanceToMoruya, approximately 20 kilometres south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMoruya Context triple: [Tuross Head, distanceToMoruya, approximately 20 kilometres south]
-
A.
distanceToMildura_km
Indicates the physical distance, measured in kilometers, between a given location and Mildura.
-
B.
distanceFromAlbury
Indicates the spatial distance between a given entity or location and the place named Albury.
-
C.
distanceFromWangaratta
Indicates the measured distance between a given location and the town of Wangaratta.
-
D.
distanceFromMurwillumbah
Indicates the spatial distance separating an entity from the location of Murwillumbah.
-
E.
distanceToMelbourne
Indicates the spatial distance between a given location or entity and the city of 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf50f4a48190a44fc537b78c32fd |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.