Triple
T31307714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis–Besse Nuclear Power Station |
E798377
|
entity |
| Predicate | reactorStatus |
P171558
|
FINISHED |
| Object | operational as of early 2020s |
—
|
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: operational as of early 2020s | Statement: [Davis–Besse Nuclear Power Station, reactorStatus, operational as of early 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorStatus Context triple: [Davis–Besse Nuclear Power Station, reactorStatus, operational as of early 2020s]
-
A.
reactorStatusDuringOccupation
Indicates the operational state of a reactor throughout a specified period of occupation or control.
-
B.
reactor
Indicates a relationship where an entity functions as or is associated with a nuclear or chemical reactor system.
-
C.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
-
D.
reactor3Commissioned
Indicates that the third reactor in a series or facility has been officially placed into service or begun operation.
-
E.
reactor4Commissioned
Indicates that the fourth reactor unit has been officially placed into service and begun operational use.
- F. None of above. chosen
Provenance (4 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:14 p.m.