Triple
T13309919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Nichols |
E317031
|
entity |
| Predicate | legalStatusInOKCBombingCase |
P75766
|
FINISHED |
| Object | not charged |
—
|
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: not charged | Statement: [James Nichols, legalStatusInOKCBombingCase, not charged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInOKCBombingCase Context triple: [James Nichols, legalStatusInOKCBombingCase, not charged]
-
A.
legalStatusInMLKCase
chosen
Indicates the legal role or standing an entity holds within the Martin Luther King Jr.–related case (e.g., defendant, plaintiff, witness, or other formal status).
-
B.
legalStatusInIraq
Indicates the legal status or standing that an entity holds under the laws and regulations of Iraq.
-
C.
numberOfPeopleKilledInBombing
Indicates the total count of people who were killed as a direct result of a specific bombing event.
-
D.
resultOfBombing
Indicates that something exists or occurs as a consequence or outcome of a bombing event.
-
E.
bombingPerpetrator
Indicates that an entity is responsible for carrying out or organizing a bombing attack against another entity or target.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.