Triple
T17603215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stirling, Western Australia |
E428757
|
entity |
| Predicate | distanceToPerthCBD |
P5889
|
FINISHED |
| Object | approximately 10 kilometres north |
—
|
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 10 kilometres north | Statement: [Stirling, Western Australia, distanceToPerthCBD, approximately 10 kilometres north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPerthCBD Context triple: [Stirling, Western Australia, distanceToPerthCBD, approximately 10 kilometres north]
-
A.
distanceToPerth
chosen
Indicates the measured distance between a given entity’s location and the city of Perth.
-
B.
distanceFromFremantle
Indicates the measured distance between a given entity and the location of Fremantle.
-
C.
distanceToMelbourne
Indicates the spatial distance between a given location or entity and the city of Melbourne.
-
D.
distanceFromFlindersStreet
Indicates the spatial distance between a given location and Flinders Street.
-
E.
distanceFromSydney
Indicates the spatial distance between a given location and the city of Sydney.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4a9a948190bc857f5da9dc7444 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b500c924819087c7107f86970675 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.