Triple
T35727711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American 4000 m summits |
E1032661
|
entity |
| Predicate | elevationCriterionType |
P6557
|
FINISHED |
| Object | topographic elevation |
—
|
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: topographic elevation | Statement: [North American 4000 m summits, elevationCriterionType, topographic elevation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationCriterionType Context triple: [North American 4000 m summits, elevationCriterionType, topographic elevation]
-
A.
elevationType
chosen
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
B.
elevationThreshold
Indicates a specified elevation level at which a condition, effect, or change in state becomes applicable or is triggered.
-
C.
hasElevationCriterionFeet
Indicates that something is associated with a specified elevation requirement or threshold measured in feet.
-
D.
hasElevationRank
Indicates the relative ordering of an entity based on its elevation compared to others.
-
E.
elevationPreference
Indicates a tendency or preference for a certain elevation or altitude relative to other possible elevation levels.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.