Triple
T32170717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homer Tunnel |
E821701
|
entity |
| Predicate | avalancheControl |
P173276
|
FINISHED |
| Object | managed avalanche control programme on approaches |
—
|
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: managed avalanche control programme on approaches | Statement: [Homer Tunnel, avalancheControl, managed avalanche control programme on approaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avalancheControl Context triple: [Homer Tunnel, avalancheControl, managed avalanche control programme on approaches]
-
A.
avalancheLocation
Indicates the location where an avalanche occurs or is situated.
-
B.
avalancheDate
Indicates the date on which an avalanche event occurred.
-
C.
hasAvalancheRisk
Indicates that there is a potential or assessed danger of an avalanche occurring in relation to the referenced entity.
-
D.
centralizesControlOf
Indicates that one entity consolidates and concentrates decision-making authority or governance power over another entity or set of entities.
-
E.
utilitiesControlledBy
Indicates that one entity has authority over, management of, or operational control of another entity’s utilities or utility services.
- F. None of above. chosen
Provenance (4 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba75252c8190991e0bb2c6452745 |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:33 a.m.