Triple
T13195360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menindee |
E314096
|
entity |
| Predicate | distanceToMajorCentre |
P106319
|
FINISHED |
| Object | approximately 100 km south-east of Broken Hill |
—
|
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 100 km south-east of Broken Hill | Statement: [Menindee, distanceToMajorCentre, approximately 100 km south-east of Broken Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMajorCentre Context triple: [Menindee, distanceToMajorCentre, approximately 100 km south-east of Broken Hill]
-
A.
distanceFromMajorPopulationCenters
chosen
Indicates the physical distance between a location and the nearest major population centers.
-
B.
distanceToWokingTownCentre
Indicates the spatial distance between a given location and the center of Woking town.
-
C.
distanceFromMajorCity
Indicates the measured distance between a given location and a specified major city.
-
D.
distanceToReadingTownCentre
Indicates the measured distance between a given location and the centre of Reading town.
-
E.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.