Triple
T29227981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Underground bombing |
E740985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional terrorist attack |
C11373
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: fictional terrorist attack Context triple: [London Underground bombing, instanceOf, fictional terrorist attack]
-
A.
terrorist attack
A terrorist attack is a deliberate act of violence or threat of violence, typically against civilians or symbolic targets, carried out to instill fear and advance political, ideological, or religious objectives.
-
B.
fictionalEvent
chosen
A fictionalEvent represents an invented occurrence or happening within a narrative world, defined by its time, place, participants, and narrative significance.
-
C.
terrorist attack target
A terrorist attack target is any person, place, system, or symbolic asset deliberately selected by terrorists to inflict harm, create fear, or achieve political, ideological, or religious objectives.
-
D.
terrorist campaign
A terrorist campaign is a sustained series of violent or coercive acts, typically carried out by non-state actors, intended to instill fear and achieve political, ideological, or religious objectives.
-
E.
fictional plan
A fictional plan is an imagined, often detailed strategy or course of action that exists only within a narrative, scenario, or conceptual context rather than in real-world implementation.
- F. None of above.
Provenance (1 batch)
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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:17 p.m.