Triple
T12864328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Augusta |
E307676
|
entity |
| Predicate | roadDistanceToWhyalla |
P107271
|
FINISHED |
| Object | about 75 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: about 75 km | Statement: [Port Augusta, roadDistanceToWhyalla, about 75 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDistanceToWhyalla Context triple: [Port Augusta, roadDistanceToWhyalla, about 75 km]
-
A.
distanceToKarratha_km
Indicates the distance, measured in kilometers, from a given location to Karratha.
-
B.
distanceFromKarratha
Indicates the measured spatial distance between a given entity or location and Karratha.
-
C.
distanceFromWaggaWagga_km
Indicates the numerical distance, measured in kilometers, between an entity’s location and Wagga Wagga.
-
D.
distanceFromCowra
Indicates the spatial distance between a given location and the place named Cowra.
-
E.
distanceToJindabyneByRoad
Indicates the length of the route between an entity and Jindabyne when traveling via the road network.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:37 p.m.