Triple
T25951008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grant Marshall |
E653964
|
entity |
| Predicate | massiveAttackRole |
P159596
|
FINISHED |
| Object | co-founder |
—
|
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: co-founder | Statement: [Grant Marshall, massiveAttackRole, co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massiveAttackRole Context triple: [Grant Marshall, massiveAttackRole, co-founder]
-
A.
killChainRole
Indicates the role an entity plays within a cyber kill chain or attack lifecycle (e.g., reconnaissance, delivery, exploitation).
-
B.
massRole
Indicates that an entity plays a specific role or function within a mass or collective context.
-
C.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
-
D.
RAFRole
Indicates that an entity holds or is assigned a specific role within the Royal Air Force.
-
E.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6049749808190a60e2e3a9e859a1f |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:44 a.m.