Triple
T32768175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuttall (hill) |
E837958
|
entity |
| Predicate | hasElevationCriterion |
P75378
|
FINISHED |
| Object | >= 2000 feet |
—
|
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: >= 2000 feet | Statement: [Nuttall (hill), hasElevationCriterion, >= 2000 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevationCriterion Context triple: [Nuttall (hill), hasElevationCriterion, >= 2000 feet]
-
A.
hasElevationCriterionFeet
chosen
Indicates that something is associated with a specified elevation requirement or threshold measured in feet.
-
B.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
C.
hasElevationRank
Indicates the relative ordering of an entity based on its elevation compared to others.
-
D.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:13 a.m.