Triple
T17373302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalanche Gulch |
E422368
|
entity |
| Predicate | descentMethod |
P127240
|
FINISHED |
| Object | downclimb |
—
|
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: downclimb | Statement: [Avalanche Gulch, descentMethod, downclimb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descentMethod Context triple: [Avalanche Gulch, descentMethod, downclimb]
-
A.
descentVia
Indicates a lineage relationship where one entity is descended from another through one or more intermediate generations or branches.
-
B.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
C.
descentSystem
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
-
D.
descendDuring
Indicates that one entity moves downward or decreases in level, altitude, or position during the time span or occurrence of another event or condition.
-
E.
hasDescent
Indicates that one entity is a descendant of another, typically through a lineage or ancestry relationship.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6a9ec881908bfe49413826d37e |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.