Triple
T31884486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windscale fire |
E813969
|
entity |
| Predicate | reactorTypeInvolved |
P3675
|
FINISHED |
| Object | air-cooled graphite-moderated reactor |
—
|
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: air-cooled graphite-moderated reactor | Statement: [Windscale fire, reactorTypeInvolved, air-cooled graphite-moderated reactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorTypeInvolved Context triple: [Windscale fire, reactorTypeInvolved, air-cooled graphite-moderated reactor]
-
A.
reactorType
chosen
Indicates the specific kind or category of reactor associated with an entity.
-
B.
reactorInvolvedInAccident
Indicates that a specific reactor participated in, contributed to, or was directly affected by a particular accident event.
-
C.
reactorTypeLicensed
Indicates that a specific type of nuclear reactor has been formally approved and licensed for use by the relevant regulatory authority.
-
D.
reactor
Indicates a relationship where an entity functions as or is associated with a nuclear or chemical reactor system.
-
E.
reactorStatus
Indicates the current operational condition or state of a reactor in relation to its functioning or safety.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 30, 2026, 11:57 p.m.