Triple
T26497623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyenchen Tanglha Main Peak |
E669324
|
entity |
| Predicate | isSacredMountainIn |
P72716
|
FINISHED |
| Object | local Tibetan folk religion |
—
|
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: local Tibetan folk religion | Statement: [Nyenchen Tanglha Main Peak, isSacredMountainIn, local Tibetan folk religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSacredMountainIn Context triple: [Nyenchen Tanglha Main Peak, isSacredMountainIn, local Tibetan folk religion]
-
A.
sacredMountainRegion
Indicates a region that is recognized or designated as a sacred mountain area.
-
B.
isRockySummitOf
Indicates that one entity is the rocky summit or peak portion of another, typically higher-level, geographic feature.
-
C.
holyMountain
chosen
Indicates that a mountain is regarded as sacred or religiously significant within a particular belief system or tradition.
-
D.
sacredHill
Indicates that a hill holds religious or spiritual significance within a belief system or tradition.
-
E.
sacredHillHeight
Indicates that a specified height value is associated with a hill regarded as sacred.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613573c548190a4a25a430a89fbf4 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:09 a.m.