Triple
T10194546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radioactive |
E238126
|
entity |
| Predicate | hasNuclearDisasterTheme |
P15089
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Radioactive, hasNuclearDisasterTheme, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNuclearDisasterTheme Context triple: [Radioactive, hasNuclearDisasterTheme, true]
-
A.
hasDisaster
chosen
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
B.
disasterDepicted
Indicates that one entity visually represents or portrays a disaster involving or affecting another entity.
-
C.
oneOfWorstNuclearAccidentsWith
Indicates that the subject is associated with another entity as being among the worst nuclear accidents together with it.
-
D.
hasNuclearPhase
Indicates that an entity undergoes or possesses a distinct stage or period characterized by nuclear-related processes, properties, or activities.
-
E.
isNonNuclear
Indicates that something does not involve, contain, or relate to nuclear weapons, nuclear power, or nuclear materials.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedc7cc748190bceb8f657afcc054 |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.