Triple
T18122029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chowchilla school bus kidnapping |
E433762
|
entity |
| Predicate | ransomDemand |
P21628
|
FINISHED |
| Object | 5000000 USD |
—
|
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: 5000000 USD | Statement: [Chowchilla school bus kidnapping, ransomDemand, 5000000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ransomDemand Context triple: [Chowchilla school bus kidnapping, ransomDemand, 5000000 USD]
-
A.
ransom
chosen
Indicates demanding payment or concessions in exchange for releasing a person, object, or information held under threat or coercion.
-
B.
ransomPaid
Indicates that a payment has been made to secure the release of a person, property, or information held under threat or coercion.
-
C.
blackmailedFor
Indicates that one entity coerces another into doing or not doing something by threatening to reveal damaging or sensitive information about them.
-
D.
surrenderDemandedBy
Indicates that one party has demanded the surrender or capitulation of another party.
-
E.
blackmails
Indicates that one entity coerces another by threatening to reveal damaging or sensitive information unless specific demands are met.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddeb2d7881909326cb9d2f5e2fb5 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.