Triple
T18934885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunaska volcanoes |
E463215
|
entity |
| Predicate | primaryHazardTarget |
P815
|
FINISHED |
| Object | aircraft on North Pacific air routes |
—
|
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: aircraft on North Pacific air routes | Statement: [Yunaska volcanoes, primaryHazardTarget, aircraft on North Pacific air routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHazardTarget Context triple: [Yunaska volcanoes, primaryHazardTarget, aircraft on North Pacific air routes]
-
A.
primaryThreat
Indicates that one entity is the main or most significant source of danger, harm, or risk to another entity.
-
B.
primaryTarget
chosen
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
C.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
primaryHeir
Indicates that one entity is the main or principal inheritor of another entity’s estate, title, or rights.
-
E.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e6a8208190973669cae439a91e |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.