Triple
T25821680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States homeland security enterprise |
E650420
|
entity |
| Predicate | addressesThreatType |
P19863
|
FINISHED |
| Object | terrorism |
—
|
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: terrorism | Statement: [United States homeland security enterprise, addressesThreatType, terrorism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesThreatType Context triple: [United States homeland security enterprise, addressesThreatType, terrorism]
-
A.
threatTypeAddressed
chosen
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
B.
targetsThreat
Indicates that one entity is directing an action or focus specifically toward a perceived threat.
-
C.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
D.
facesThreat
Indicates that an entity is exposed to or confronted by a potential danger, risk, or harmful situation.
-
E.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60191786c81908ee95f5d74dfe98a |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:30 a.m.