Triple
T29823273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sally Hurst |
E757307
|
entity |
| Predicate | threatLocation |
P173266
|
FINISHED |
| Object | inside the 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: inside the house | Statement: [Sally Hurst, threatLocation, inside the house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatLocation Context triple: [Sally Hurst, threatLocation, inside the house]
-
A.
threatEncounteredNear
Indicates that a threat was encountered in close spatial proximity to a specified reference point or entity.
-
B.
threatType
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. 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 29, 2026, 5:30 p.m.