Triple
T26387105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OKBOMB |
E663309
|
entity |
| Predicate | handledByOffice |
P138314
|
FINISHED |
| Object | FBI Oklahoma City Field Office |
—
|
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 Oklahoma City Field Office | Statement: [OKBOMB, handledByOffice, FBI Oklahoma City Field Office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledByOffice Context triple: [OKBOMB, handledByOffice, FBI Oklahoma City Field Office]
-
A.
handedOverOfficeDuring
Indicates that one entity transferred official control, authority, or responsibility of an office or position to another entity during a specified time period.
-
B.
handledIn
chosen
Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
-
C.
subjectOffice
Indicates the office or official position held by the subject in relation to another entity or context.
-
D.
controlledOffice
Indicates that one entity has authority over, manages, or directs the operations of a particular office or administrative location.
-
E.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
- 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_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:23 p.m.