Triple
T28813334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 北岳 |
E727573
|
entity |
| Predicate | 危険要因 |
P149293
|
FINISHED |
| Object | 急峻なガレ場や落石の危険がある |
—
|
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: 急峻なガレ場や落石の危険がある | Statement: [北岳, 危険要因, 急峻なガレ場や落石の危険がある]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 危険要因 Context triple: [北岳, 危険要因, 急峻なガレ場や落石の危険がある]
-
A.
hasRiskFactorFor
chosen
Indicates that one entity contributes to or increases the likelihood of another entity experiencing a particular risk or adverse outcome.
-
B.
riskFactorForDeath
Indicates that something increases the likelihood or probability of death occurring.
-
C.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
D.
riskFactorTypeStudied
Indicates that a particular type of risk factor is the subject of study or analysis in a given context.
-
E.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.