Triple
T21626543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qunaba |
E533718
|
entity |
| Predicate | distanceToBundabergCBD |
P64989
|
FINISHED |
| Object | approximately 10 km east (approximate) |
—
|
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 10 km east (approximate) | Statement: [Qunaba, distanceToBundabergCBD, approximately 10 km east (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBundabergCBD Context triple: [Qunaba, distanceToBundabergCBD, approximately 10 km east (approximate)]
-
A.
distanceToBundaberg
chosen
Indicates the measured distance between a given location or entity and the city of Bundaberg.
-
B.
distanceToHerveyBayCBD_km
Indicates the distance, measured in kilometers, between a given location and the central business district (CBD) of Hervey Bay.
-
C.
distanceFromBrisbane
Indicates the measured distance between a given location or entity and the city of Brisbane.
-
D.
distanceToNambour
Indicates the spatial distance between a given entity and the location of Nambour.
-
E.
distanceToBrisbane_km
Indicates the physical distance, measured in kilometers, between a given location and Brisbane.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52131f2c8190b9966adf43a0fe4f |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.