Triple
T16939549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sedan test |
E410914
|
entity |
| Predicate | falloutImpact |
P103809
|
FINISHED |
| Object | produced significant radioactive fallout |
—
|
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: produced significant radioactive fallout | Statement: [Sedan test, falloutImpact, produced significant radioactive fallout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: falloutImpact Context triple: [Sedan test, falloutImpact, produced significant radioactive fallout]
-
A.
fallout
chosen
Indicates the negative consequences or residual effects that result from a prior event, action, or conflict.
-
B.
falloutType
Indicates the specific kind or category of fallout that results from an event, action, or condition.
-
C.
dateOfMajorFalloutExposure
Indicates the specific date on which a subject experienced significant exposure to radioactive fallout.
-
D.
capitalAftermath
Indicates that one entity is the consequence, result, or follow-up state of another entity’s capital-related event or situation.
-
E.
affectedCivilization
Indicates that one civilization has experienced an impact, influence, or change as a result of another entity, event, or process.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2c44288190a105761ae646989e |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.