Triple
T31032232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unit 4 reactor building |
E790757
|
entity |
| Predicate | dateOfHydrogenExplosion |
P89936
|
FINISHED |
| Object | 2011-03-15 |
—
|
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: 2011-03-15 | Statement: [Unit 4 reactor building, dateOfHydrogenExplosion, 2011-03-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfHydrogenExplosion Context triple: [Unit 4 reactor building, dateOfHydrogenExplosion, 2011-03-15]
-
A.
hydrogenExplosionDate
chosen
Indicates the date on which a hydrogen explosion occurred or is scheduled to occur.
-
B.
explosionDateApprox
Indicates that an explosion occurred on or around a specified date, where the exact date is not known or is only approximate.
-
C.
hydrogenExplosionsOccurredIn
Indicates that one or more hydrogen explosions took place at the specified location or within the specified context.
-
D.
bombardmentDate
Indicates the date on which a bombardment event occurred or was carried out.
-
E.
dateOfTragedy
Indicates the specific calendar date on which a tragic event occurred.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 8:59 p.m.