Triple
T16190413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grandma Gilmore |
E392922
|
entity |
| Predicate | threatInStory |
P122093
|
FINISHED |
| Object | loss of her house |
—
|
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: loss of her house | Statement: [Grandma Gilmore, threatInStory, loss of her house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatInStory Context triple: [Grandma Gilmore, threatInStory, loss of her house]
-
A.
threatContained
Indicates that an identified threat has been successfully neutralized, controlled, or otherwise prevented from causing further harm or escalation.
-
B.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
-
D.
threatContext
Indicates the situational conditions, factors, or environment in which a threat occurs or is relevant.
-
E.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
- F. None of above. chosen
Provenance (4 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d4ab8081909a02e5138b29b83b |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.