Triple
T30110556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Butte |
E765257
|
entity |
| Predicate | elevationRankInNorthDakota |
P85480
|
FINISHED |
| Object | highest natural point |
—
|
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: highest natural point | Statement: [White Butte, elevationRankInNorthDakota, highest natural point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationRankInNorthDakota Context triple: [White Butte, elevationRankInNorthDakota, highest natural point]
-
A.
summitElevationNorth
Indicates the elevation of the summit located to the north relative to a given reference point or feature.
-
B.
rankInNorthAmericaByElevation
Indicates the relative position of a place in an ordered list of locations in North America based on their elevation.
-
C.
hasCountyNumberInNorthDakota
Indicates that a county is assigned a specific official county number within the state of North Dakota.
-
D.
hasElevationRank
Indicates the relative ordering of an entity based on its elevation compared to others.
-
E.
stateHighPointRank
chosen
Indicates the relative ranking position of a location as the highest point within a given state or comparable region.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 7:10 p.m.