Triple
T26386998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryder rental truck |
E663307
|
entity |
| Predicate | cityOfDetonation |
P160584
|
FINISHED |
| Object | Oklahoma City |
—
|
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: Oklahoma City | Statement: [Ryder rental truck, cityOfDetonation, Oklahoma City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfDetonation Context triple: [Ryder rental truck, cityOfDetonation, Oklahoma City]
-
A.
deathCity
Indicates the city in which an entity (typically a person) died.
-
B.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
-
C.
detonatedOutside
Indicates that an explosive device was set off in a location that is outside a specified area or structure.
-
D.
detonatedBy
Indicates that an explosive or device is set off or caused to explode by a particular agent or entity.
-
E.
destroyedCity
Indicates that an entity has caused the complete or near-complete destruction of a city.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 11:23 p.m.