Triple
T15006032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coolamon, New South Wales |
E377713
|
entity |
| Predicate | distanceTo Sydney |
P15398
|
FINISHED |
| Object | approximately 500 kilometres southwest |
—
|
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 500 kilometres southwest | Statement: [Coolamon, New South Wales, distanceTo Sydney, approximately 500 kilometres southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTo Sydney Context triple: [Coolamon, New South Wales, distanceTo Sydney, approximately 500 kilometres southwest]
-
A.
distanceFromSydney
chosen
Indicates the spatial distance between a given location and the city of Sydney.
-
B.
distanceToAustralia
Indicates the measured or estimated spatial distance between a given entity and Australia.
-
C.
distanceToMelbourne
Indicates the spatial distance between a given location or entity and the city of Melbourne.
-
D.
distanceToDarwin
Indicates the spatial distance between a given entity’s location and the location of Darwin.
-
E.
distanceToGoldCoast
Indicates the measured distance between a given entity and the location known as the Gold Coast.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7322b5c81909089cbbf816e1436 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.