Triple
T21646562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohlaubgrat (east ridge) |
E534232
|
entity |
| Predicate | descentOption |
P127240
|
FINISHED |
| Object | normal route of Allalinhorn |
—
|
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: normal route of Allalinhorn | Statement: [Hohlaubgrat (east ridge), descentOption, normal route of Allalinhorn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descentOption Context triple: [Hohlaubgrat (east ridge), descentOption, normal route of Allalinhorn]
-
A.
descentVia
Indicates a lineage relationship where one entity is descended from another through one or more intermediate generations or branches.
-
B.
descentStageUsedFor
Indicates that a particular descent stage is utilized to support or perform an associated mission, operation, or vehicle activity.
-
C.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
D.
descentSystem
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
-
E.
descentMethod
chosen
Indicates the technique or process used to descend from a higher position, level, or altitude.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef591194dc8190a57b28eaddeceff5 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.