Triple
T23976145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pemi Loop |
E604372
|
entity |
| Predicate | includesPeakOver4000Feet |
P86531
|
FINISHED |
| Object | Mount Lafayette |
—
|
NE NERFINISHED |
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: Mount Lafayette | Statement: [Pemi Loop, includesPeakOver4000Feet, Mount Lafayette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPeakOver4000Feet Context triple: [Pemi Loop, includesPeakOver4000Feet, Mount Lafayette]
-
A.
hasPeakAbove4000m
Indicates that an entity possesses at least one peak whose elevation exceeds 4000 meters.
-
B.
hasSummitOver4000m
Indicates that the referenced geographic feature includes at least one summit whose elevation exceeds 4000 meters above sea level.
-
C.
isConsideredFourteenerBy
Indicates that one entity is regarded or classified by another entity as a “fourteener” (typically a mountain with an elevation of at least 14,000 feet).
-
D.
hasPeakOver3000m
Indicates that the related geographic feature has at least one peak whose elevation exceeds 3000 meters above sea level.
-
E.
includesSummitsOverFeet
chosen
Indicates that something contains or encompasses mountain summits whose elevations exceed a specified number of feet.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2ba11708190b8587bd006249ff5 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:26 p.m.