Triple
T37022131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Gorge |
E916249
|
entity |
| Predicate | hasDistanceFrom |
P120034
|
FINISHED |
| Object | approximately 250 km east of Derby, Western Australia |
—
|
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 250 km east of Derby, Western Australia | Statement: [Bell Gorge, hasDistanceFrom, approximately 250 km east of Derby, Western Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceFrom Context triple: [Bell Gorge, hasDistanceFrom, approximately 250 km east of Derby, Western Australia]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
hasDistanceElement
Indicates that one entity includes or is associated with a component that specifies a distance value or measurement.
-
C.
hasDistanceReference
Indicates that a distance value is specified relative to a particular reference point, scale, or standard.
-
D.
distancesFrom
chosen
Indicates the measured spatial separation between one entity and one or more other entities.
-
E.
hasCommonDistance
Indicates that two or more entities share the same measured distance value between them.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:14 p.m.