Triple
T28664514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio Penitentiary |
E725551
|
entity |
| Predicate | deathTollEvent |
P126019
|
FINISHED |
| Object | one of the deadliest prison fires in U.S. history |
—
|
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: one of the deadliest prison fires in U.S. history | Statement: [Ohio Penitentiary, deathTollEvent, one of the deadliest prison fires in U.S. history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathTollEvent Context triple: [Ohio Penitentiary, deathTollEvent, one of the deadliest prison fires in U.S. history]
-
A.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
B.
notableDeathTollEvent
chosen
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
-
C.
deathDuringEvent
Indicates that an entity died while a specified event was occurring.
-
D.
deathTollEstimate
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
-
E.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 5 a.m.