Triple
T14419467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomona |
E357542
|
entity |
| Predicate | distanceToNoosaHeads |
P114185
|
FINISHED |
| Object | approximately 30 km |
—
|
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 km | Statement: [Pomona, distanceToNoosaHeads, approximately 30 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNoosaHeads Context triple: [Pomona, distanceToNoosaHeads, approximately 30 km]
-
A.
distanceToNarooma
Indicates the measured spatial distance between a given entity and the location Narooma.
-
B.
distanceToMaroochydore
Indicates the measured distance from a given entity or location to Maroochydore.
-
C.
distanceToMoruya
Indicates the measured or calculated distance between a given entity or location and Moruya.
-
D.
distanceToByronBay
Indicates the spatial distance between a given location or entity and Byron Bay.
-
E.
distanceToForster_km
Indicates the physical distance, measured in kilometers, between an entity and a reference location named Forster.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de910eb354819089d5d5a46919eb49 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.