Triple
T4226483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dandenong, Victoria |
E94470
|
entity |
| Predicate | distanceToMelbourneCBD |
P21893
|
FINISHED |
| Object | approximately 30 kilometres south-east |
—
|
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 kilometres south-east | Statement: [Dandenong, Victoria, distanceToMelbourneCBD, approximately 30 kilometres south-east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMelbourneCBD Context triple: [Dandenong, Victoria, distanceToMelbourneCBD, approximately 30 kilometres south-east]
-
A.
distanceToMelbourne
chosen
Indicates the spatial distance between a given location or entity and the city of Melbourne.
-
B.
distanceFromSydney
Indicates the spatial distance between a given location and the city of Sydney.
-
C.
distanceFromGeelong
Indicates the spatial distance between a given entity or location and Geelong.
-
D.
distanceToMildura_km
Indicates the physical distance, measured in kilometers, between a given location and Mildura.
-
E.
distanceToAdelaide_km
Indicates the physical distance, measured in kilometers, between a given location and Adelaide.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e4ed34c819081d1479ce87cd78c |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.