Triple
T26387104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OKBOMB |
E663309
|
entity |
| Predicate | handledByUnit |
P71354
|
FINISHED |
| Object | FBI Counterterrorism components |
—
|
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: FBI Counterterrorism components | Statement: [OKBOMB, handledByUnit, FBI Counterterrorism components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledByUnit Context triple: [OKBOMB, handledByUnit, FBI Counterterrorism components]
-
A.
handledIn
Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
-
B.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
-
C.
handledMatter
chosen
Indicates that an entity has dealt with, managed, or taken responsibility for a particular matter, issue, or case.
-
D.
assignedToUnit
Indicates that an entity (such as a person, resource, or task) is allocated or designated to a specific unit or organizational subdivision.
-
E.
operatedByUnit
Indicates that an entity (such as a system, device, or facility) is run, controlled, or managed by a specific organizational unit.
- 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_69f610bc2b288190ae10e6c27e5df786 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:23 p.m.