Triple
T25040896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbes, New South Wales |
E627103
|
entity |
| Predicate | distanceFromParkes |
P170324
|
FINISHED |
| Object | approximately 33 kilometres south of Parkes |
—
|
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 33 kilometres south of Parkes | Statement: [Forbes, New South Wales, distanceFromParkes, approximately 33 kilometres south of Parkes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromParkes Context triple: [Forbes, New South Wales, distanceFromParkes, approximately 33 kilometres south of Parkes]
-
A.
distanceFromSydney
Indicates the spatial distance between a given location and the city of Sydney.
-
B.
distanceToPerisherByRoad
Indicates the road travel distance required to reach Perisher from a given location.
-
C.
distanceFromMoree
Indicates the spatial distance measured from the reference location Moree to another place or entity.
-
D.
distanceToUluru
Indicates the spatial distance between a given entity and Uluru.
-
E.
distanceFromGosford_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Gosford.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 18, 2026, 6:08 a.m.