Triple
T6430175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast Ridge route |
E128158
|
entity |
| Predicate | SecondStepElevation |
P70847
|
FINISHED |
| Object | around 8610 m |
—
|
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: around 8610 m | Statement: [Northeast Ridge route, SecondStepElevation, around 8610 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SecondStepElevation Context triple: [Northeast Ridge route, SecondStepElevation, around 8610 m]
-
A.
secondStage
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
-
B.
secondStageType
Indicates the specific kind or category of a process, object, or event that occurs as the second stage in a multi-stage sequence.
-
C.
secondTier
Indicates that something occupies a secondary or subordinate level of importance, quality, or rank relative to a primary or top tier.
-
D.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
E.
secondElement
Indicates that one entity is the second element in an ordered pair, sequence, or collection relative to another entity.
- F. None of above. chosen
Provenance (4 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693b872c819082a7d0e257018831 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c062d290448190a2183158ef75d129 |
completed | March 22, 2026, 9:44 p.m. |
Created at: March 22, 2026, 4:44 p.m.