Triple
T25618388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castlemaine, Victoria, Australia |
E642223
|
entity |
| Predicate | distanceFromBendigo |
P184833
|
FINISHED |
| Object | approximately 40 kilometres south |
—
|
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 40 kilometres south | Statement: [Castlemaine, Victoria, Australia, distanceFromBendigo, approximately 40 kilometres south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBendigo Context triple: [Castlemaine, Victoria, Australia, distanceFromBendigo, approximately 40 kilometres south]
-
A.
distanceFromGeelong
Indicates the spatial distance between a given entity or location and Geelong.
-
B.
distanceFromAlbury
Indicates the spatial distance between a given entity or location and the place named Albury.
-
C.
distanceToMildura_km
Indicates the physical distance, measured in kilometers, between a given location and Mildura.
-
D.
distanceFromWangaratta
Indicates the measured distance between a given location and the town of Wangaratta.
-
E.
distanceToCaloundra
Indicates the spatial distance between a given location and Caloundra.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 21, 2026, 5:02 p.m.