Triple
T34455820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Mountain, Minnesota |
E884500
|
entity |
| Predicate | USStateHighPointOf |
P178960
|
FINISHED |
| Object | Minnesota |
—
|
NE NERFINISHED |
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: Minnesota | Statement: [Eagle Mountain, Minnesota, USStateHighPointOf, Minnesota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USStateHighPointOf Context triple: [Eagle Mountain, Minnesota, USStateHighPointOf, Minnesota]
-
A.
recognizedAsStateHighPointSince
Indicates that an entity has been officially acknowledged as the highest point of a state starting from a specified date or time.
-
B.
stateHighestPointAccess
Indicates that a state’s highest geographical point can be accessed or reached by a specified means or under certain conditions.
-
C.
trailHighPointOf
Indicates that one location is the highest elevation point along a specified trail or route.
-
D.
stateHighPointRank
Indicates the relative ranking position of a location as the highest point within a given state or comparable region.
-
E.
highestPointWestOf
Indicates that one location is the highest-elevation point among all locations situated to the west of a specified reference location.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.