Triple
T32686599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redbank Plains |
E835742
|
entity |
| Predicate | distanceToBrisbaneCBD_km |
P39331
|
FINISHED |
| Object | approximately 30 |
—
|
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 30 | Statement: [Redbank Plains, distanceToBrisbaneCBD_km, approximately 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBrisbaneCBD_km Context triple: [Redbank Plains, distanceToBrisbaneCBD_km, approximately 30]
-
A.
distanceToBrisbane_km
chosen
Indicates the physical distance, measured in kilometers, between a given location and Brisbane.
-
B.
distanceFromBrisbane
Indicates the measured distance between a given location or entity and the city of Brisbane.
-
C.
distanceToHerveyBayCBD_km
Indicates the distance, measured in kilometers, between a given location and the central business district (CBD) of Hervey Bay.
-
D.
distanceToQueanbeyanCBD_km
Indicates the distance, measured in kilometers, from an entity to the central business district of Queanbeyan.
-
E.
distanceToHerveyBay_km
Indicates the distance, measured in kilometers, between a given location and Hervey Bay.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:09 a.m.