Triple
T25953951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1970 Nanga Parbat expedition |
E654044
|
entity |
| Predicate | descentFace |
P159229
|
FINISHED |
| Object | Diamir Face |
—
|
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: Diamir Face | Statement: [1970 Nanga Parbat expedition, descentFace, Diamir Face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descentFace Context triple: [1970 Nanga Parbat expedition, descentFace, Diamir Face]
-
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.
descentTarget
chosen
Indicates that an entity is the intended destination or endpoint toward which another entity is descending.
-
D.
descentSystem
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
-
E.
descentStageUsedFor
Indicates that a particular descent stage is utilized to support or perform an associated mission, operation, or vehicle activity.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6049a5508819085be78ba6fbbfd69 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:44 a.m.