Triple
T19674905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Ash |
E472426
|
entity |
| Predicate | distanceToNelsonBay_km |
P136506
|
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: [Salt Ash, distanceToNelsonBay_km, approximately 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNelsonBay_km Context triple: [Salt Ash, distanceToNelsonBay_km, approximately 30]
-
A.
distanceToHerveyBay_km
Indicates the distance, measured in kilometers, between a given location and Hervey Bay.
-
B.
distanceToHerveyBayCBD_km
Indicates the distance, measured in kilometers, between a given location and the central business district (CBD) of Hervey Bay.
-
C.
distanceToForster_km
Indicates the physical distance, measured in kilometers, between an entity and a reference location named Forster.
-
D.
distanceToNoosaHeads_km
Indicates the physical distance, measured in kilometers, between a given location and Noosa Heads.
-
E.
distanceToGreatSandyStrait
Indicates the measured distance between an entity’s location and the Great Sandy Strait.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bb2b7c8190b2badf12ce2caa52 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:45 p.m.