Triple
T3069212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockingham |
E62178
|
entity |
| Predicate | distanceFromPerthCBD |
P5889
|
FINISHED |
| Object | approximately 47 kilometres south-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 47 kilometres south-southwest | Statement: [Rockingham, distanceFromPerthCBD, approximately 47 kilometres south-southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromPerthCBD Context triple: [Rockingham, distanceFromPerthCBD, approximately 47 kilometres south-southwest]
-
A.
distanceToPerth
chosen
Indicates the measured distance between a given entity’s location and the city of Perth.
-
B.
distanceFromWaggaWagga_km
Indicates the numerical distance, measured in kilometers, between an entity’s location and Wagga Wagga.
-
C.
distanceFromSydney
Indicates the spatial distance between a given location and the city of Sydney.
-
D.
distanceFromBrisbane
Indicates the measured distance between a given location or entity and the city of Brisbane.
-
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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0ffcc208190962cc9edcbf43c31 |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.