Triple
T9992792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amberley, Queensland |
E196927
|
entity |
| Predicate | distanceToIpswichCBD |
P60998
|
FINISHED |
| Object | approximately 15 kilometres southwest |
—
|
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 15 kilometres southwest | Statement: [Amberley, Queensland, distanceToIpswichCBD, approximately 15 kilometres southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToIpswichCBD Context triple: [Amberley, Queensland, distanceToIpswichCBD, approximately 15 kilometres southwest]
-
A.
distanceToIpswich
chosen
Indicates the spatial distance between a given location and the town or area of Ipswich.
-
B.
distanceToWorcester
Indicates the measured distance between a given entity’s location and the city of Worcester.
-
C.
distanceToWisbech
Indicates the spatial distance between a given location or entity and the town of Wisbech.
-
D.
distanceFromCambridgeCentre
Indicates the spatial distance between a given entity and the central point of Cambridge.
-
E.
distanceToShrewsbury
Indicates the measured distance between a given entity or location and the town of Shrewsbury.
- F. None of above.
Provenance (3 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcb96c7308190902802ef5df764c1 |
completed | April 2, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.