Triple
T35476654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridgeway, Tasmania |
E1025351
|
entity |
| Predicate | distanceToCentralHobart_km |
P60312
|
FINISHED |
| Object | approximately 5–10 kilometres |
—
|
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 5–10 kilometres | Statement: [Ridgeway, Tasmania, distanceToCentralHobart_km, approximately 5–10 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCentralHobart_km Context triple: [Ridgeway, Tasmania, distanceToCentralHobart_km, approximately 5–10 kilometres]
-
A.
distanceFromHobart
chosen
Indicates the spatial distance between a given entity and the location of Hobart.
-
B.
distanceFromWaggaWagga_km
Indicates the numerical distance, measured in kilometers, between an entity’s location and Wagga Wagga.
-
C.
distanceToWarrnambool_km
Indicates the measured distance, in kilometers, from a given entity or location to Warrnambool.
-
D.
distanceFromGosford_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Gosford.
-
E.
distanceToHerveyBayCBD_km
Indicates the distance, measured in kilometers, between a given location and the central business district (CBD) of Hervey Bay.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.