Triple
T34455839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Mountain, Minnesota |
E884500
|
entity |
| Predicate | stateHighPointRankByElevationInUS |
P85480
|
FINISHED |
| Object | 38 |
—
|
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: 38 | Statement: [Eagle Mountain, Minnesota, stateHighPointRankByElevationInUS, 38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighPointRankByElevationInUS Context triple: [Eagle Mountain, Minnesota, stateHighPointRankByElevationInUS, 38]
-
A.
stateHighPointRank
chosen
Indicates the relative ranking position of a location as the highest point within a given state or comparable region.
-
B.
rankingInStateByHeight
Indicates the position an entity holds in an ordered list of entities within a specific state, based on their relative height.
-
C.
USStateHighPointOf
Indicates that a location is the highest natural elevation point within a specific U.S. state.
-
D.
rankAmongTallestInUS
Indicates that the entity is among the tallest of its kind within the United States.
-
E.
rankInNorthAmericaByElevation
Indicates the relative position of a place in an ordered list of locations in North America based on their elevation.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 1, 2026, 2 a.m.