Triple
T19378494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrnambool region |
E484732
|
entity |
| Predicate | distanceToMelbourneByRoad |
P21893
|
FINISHED |
| Object | approximately 260 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 260 km | Statement: [Warrnambool region, distanceToMelbourneByRoad, approximately 260 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMelbourneByRoad Context triple: [Warrnambool region, distanceToMelbourneByRoad, approximately 260 km]
-
A.
distanceToMelbourne
chosen
Indicates the spatial distance between a given location or entity and the city of Melbourne.
-
B.
approxDrivingTimeFromMelbourne
Indicates the estimated duration it takes to drive from Melbourne to a specified location.
-
C.
distanceFromSydney
Indicates the spatial distance between a given location and the city of Sydney.
-
D.
distanceToAdelaide_km
Indicates the physical distance, measured in kilometers, between a given location and Adelaide.
-
E.
distanceToPerisherByRoad
Indicates the road travel distance required to reach Perisher from a given location.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5dc3048190830b55c8ca02e624 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.