Triple
T11369212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machapuchare |
E269296
|
entity |
| Predicate | climbingReasonForBan |
P25587
|
FINISHED |
| Object | religious sanctity |
—
|
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: religious sanctity | Statement: [Machapuchare, climbingReasonForBan, religious sanctity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingReasonForBan Context triple: [Machapuchare, climbingReasonForBan, religious sanctity]
-
A.
climbingBanEffectiveFrom
Indicates the date or point in time from which a climbing ban starts to apply.
-
B.
reasonForBan
chosen
Indicates the justification or cause that led to an entity being banned.
-
C.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
-
D.
climbingRegulations
Indicates rules or restrictions governing how climbing activities may be conducted in a given area or context.
-
E.
climbedPrimarilyFor
Indicates that the primary purpose or motivation for someone climbing something was for the specified reason or goal.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.