Triple
T18858714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulanga River |
E461247
|
entity |
| Predicate | threatTypeInStory |
P50110
|
FINISHED |
| Object | natural danger |
—
|
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: natural danger | Statement: [Ulanga River, threatTypeInStory, natural danger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatTypeInStory Context triple: [Ulanga River, threatTypeInStory, natural danger]
-
A.
threatInStory
Indicates that one entity poses or represents a danger, menace, or harmful intent toward another entity within the context of a narrative or story.
-
B.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
D.
threatContained
Indicates that an identified threat has been successfully neutralized, controlled, or otherwise prevented from causing further harm or escalation.
-
E.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05eaee881909da704cf1374158c |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.