Triple
T9109005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast 111 4000-footers |
E218546
|
entity |
| Predicate | hasElevationThreshold |
P75378
|
FINISHED |
| Object | 4000 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: 4000 feet | Statement: [Northeast 111 4000-footers, hasElevationThreshold, 4000 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevationThreshold Context triple: [Northeast 111 4000-footers, hasElevationThreshold, 4000 feet]
-
A.
elevationThreshold
Indicates a specified elevation level at which a condition, effect, or change in state becomes applicable or is triggered.
-
B.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
C.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
D.
hasElevationCriterionFeet
chosen
Indicates that something is associated with a specified elevation requirement or threshold measured in feet.
-
E.
isHighElevation
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca57543448190829853c31e05dd8c |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.