Triple
T871994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Service (MI5) |
E18832
|
entity |
| Predicate | focusesOnThreat |
P31
|
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: [Security Service (MI5), focusesOnThreat, terrorism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnThreat Context triple: [Security Service (MI5), focusesOnThreat, terrorism]
-
A.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
historicalThreat
Indicates that one entity posed a significant threat to another in the past, but is not necessarily a current or ongoing danger.
-
D.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
-
E.
missionFocus
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac96850881908a2d776685126137 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.