Triple
T13077110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smoking Mountain |
E329605
|
entity |
| Predicate | climbingRestricted |
P46978
|
FINISHED |
| Object | often, due to volcanic activity |
—
|
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: often, due to volcanic activity | Statement: [Smoking Mountain, climbingRestricted, often, due to volcanic activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingRestricted Context triple: [Smoking Mountain, climbingRestricted, often, due to volcanic activity]
-
A.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
-
B.
climbingAccess
Indicates that one entity provides permission, routes, or means for another entity to engage in climbing activities at a particular location or structure.
-
C.
climbingRegulations
chosen
Indicates rules or restrictions governing how climbing activities may be conducted in a given area or context.
-
D.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within another entity.
-
E.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9811828448190ac6ddd3e9c221251 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:01 p.m.