Triple
T4678914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aiguille Verte |
E103748
|
entity |
| Predicate | danger |
P50110
|
FINISHED |
| Object | avalanches |
—
|
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: avalanches | Statement: [Aiguille Verte, danger, avalanches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danger Context triple: [Aiguille Verte, danger, avalanches]
-
A.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
-
B.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
C.
risk
Indicates that one entity is exposed or subject to potential harm, loss, or adverse outcome arising from another entity, action, or situation.
-
D.
death
Indicates the event or state in which an entity ceases to live or exist, marking the end of its biological or functional processes.
-
E.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.