Triple
T20227330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overlord Mountain |
E495419
|
entity |
| Predicate | avalancheRisk |
P108313
|
FINISHED |
| Object | significant in winter and spring |
—
|
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: significant in winter and spring | Statement: [Overlord Mountain, avalancheRisk, significant in winter and spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avalancheRisk Context triple: [Overlord Mountain, avalancheRisk, significant in winter and spring]
-
A.
hasAvalancheRisk
chosen
Indicates that there is a potential or assessed danger of an avalanche occurring in relation to the referenced entity.
-
B.
volcanicRiskArea
Indicates that a location lies within an area exposed to potential hazards from volcanic activity, such as eruptions, ashfall, or lava flows.
-
C.
riskToEarth
Indicates that something poses a potential threat, danger, or harmful impact to Earth.
-
D.
AlexanderRisk
Indicates a relationship where Alexander is exposed to, associated with, or responsible for a particular risk or potential adverse outcome.
-
E.
geologicHazardLevel
Indicates the degree of potential danger or risk posed by geologic processes or conditions at a given location.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fda9428819098467e7e8c547a07 |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.