Triple
T4644041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Kailash |
E101720
|
entity |
| Predicate | climbingPolicy |
P46978
|
FINISHED |
| Object | ascent prohibited for religious reasons |
—
|
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: ascent prohibited for religious reasons | Statement: [Mount Kailash, climbingPolicy, ascent prohibited for religious reasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingPolicy Context triple: [Mount Kailash, climbingPolicy, ascent prohibited for religious reasons]
-
A.
climbingRegulations
chosen
Indicates rules or restrictions governing how climbing activities may be conducted in a given area or context.
-
B.
climbPerformance
Indicates how effectively or rapidly an entity ascends or gains altitude relative to conditions or expectations.
-
C.
climbingBanEffectiveFrom
Indicates the date or point in time from which a climbing ban starts to apply.
-
D.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
E.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.