Triple
T26387078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OKBOMB |
E663309
|
entity |
| Predicate | primarySuspect |
P21177
|
FINISHED |
| Object | Timothy McVeigh |
—
|
NE NERFINISHED |
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: Timothy McVeigh | Statement: [OKBOMB, primarySuspect, Timothy McVeigh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySuspect Context triple: [OKBOMB, primarySuspect, Timothy McVeigh]
-
A.
hasSuspect
Indicates that an entity is identified or considered as a suspect in relation to another entity or incident.
-
B.
suspectedPerpetrator
chosen
Indicates that an entity is believed or alleged to be the person responsible for committing a particular harmful or illegal act.
-
C.
isSuspiciousOf
Indicates that one entity believes another entity or situation may be untrustworthy, harmful, or involved in wrongdoing.
-
D.
primaryThreat
Indicates that one entity is the main or most significant source of danger, harm, or risk to another entity.
-
E.
primarySin
Indicates a fundamental or chief moral wrongdoing attributed to an entity, often viewed as the root or most significant sin in a given context.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 26, 2026, 11:23 p.m.