Triple
T35795913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kootenay Pass |
E1034829
|
entity |
| Predicate | avalancheControlMethods |
P173276
|
FINISHED |
| Object | artillery |
—
|
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: artillery | Statement: [Kootenay Pass, avalancheControlMethods, artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avalancheControlMethods Context triple: [Kootenay Pass, avalancheControlMethods, artillery]
-
A.
avalancheControl
chosen
Indicates actions or measures taken to prevent, reduce, or manage the risk and impact of avalanches.
-
B.
avalancheLocation
Indicates the location where an avalanche occurs or is situated.
-
C.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of another entity.
-
D.
hasAvalancheRisk
Indicates that there is a potential or assessed danger of an avalanche occurring in relation to the referenced entity.
-
E.
avalancheDate
Indicates the date on which an avalanche event occurred.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a25541c081909a2c3780af82c516 |
completed | May 3, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.