Triple
T15556495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirranbandi |
E370882
|
entity |
| Predicate | distanceToStGeorge_km |
P119162
|
FINISHED |
| Object | approximately 95 |
—
|
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 95 | Statement: [Dirranbandi, distanceToStGeorge_km, approximately 95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToStGeorge_km Context triple: [Dirranbandi, distanceToStGeorge_km, approximately 95]
-
A.
distanceFromGeelong
Indicates the spatial distance between a given entity or location and Geelong.
-
B.
distanceFromGeorgeTown
Indicates the measured spatial distance between a given location and George Town.
-
C.
distanceToAdelaide_km
Indicates the physical distance, measured in kilometers, between a given location and Adelaide.
-
D.
distanceToForster_km
Indicates the physical distance, measured in kilometers, between an entity and a reference location named Forster.
-
E.
distanceToGympie
Indicates the spatial distance between a given location and the town or area of Gympie.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a97dbfc8190a98cbbac5e71ba88 |
completed | April 16, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:09 a.m.