Triple
T19886950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alma, Colorado |
E477923
|
entity |
| Predicate | altitudeRanking |
P136632
|
FINISHED |
| Object | among the highest towns in North America |
—
|
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: among the highest towns in North America | Statement: [Alma, Colorado, altitudeRanking, among the highest towns in North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeRanking Context triple: [Alma, Colorado, altitudeRanking, among the highest towns in North America]
-
A.
summitElevationRank
Indicates the relative position of a summit in an ordered list based on its elevation compared to other summits.
-
B.
regionRankByHeight
Indicates the relative ordering of regions based on their height or elevation.
-
C.
hasElevationRank
chosen
Indicates the relative ordering of an entity based on its elevation compared to others.
-
D.
FIDERankingPeak
Indicates the highest FIDE (chess) rating or ranking position an entity has ever achieved.
-
E.
altitudeCategory
Indicates the classification of something based on its height or elevation relative to a reference level (e.g., low, medium, high altitude).
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590b12c08190bf44a3f3b2cb9122 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.