Triple
T38006411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953 Nanga Parbat expedition |
E948245
|
entity |
| Predicate | targetMountain |
P199738
|
FINISHED |
| Object | Nanga Parbat main summit |
—
|
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: Nanga Parbat main summit | Statement: [1953 Nanga Parbat expedition, targetMountain, Nanga Parbat main summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetMountain Context triple: [1953 Nanga Parbat expedition, targetMountain, Nanga Parbat main summit]
-
A.
homeMountainOf
Indicates that a particular mountain is the primary or native mountain associated with a given entity (such as a person, group, or organization).
-
B.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
-
C.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
-
D.
mountainAccess
Indicates that an entity has the ability, right, or means to reach, enter, or utilize a mountain or mountainous area.
-
E.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69ff528536d481909caefe52fcd8aaa7 |
completed | May 9, 2026, 3:28 p.m. |
Created at: May 3, 2026, 4:20 p.m.