Triple
T31713111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWR-3 |
E809379
|
entity |
| Predicate | usedFuelCycle |
P163628
|
FINISHED |
| Object | once-through fuel cycle |
—
|
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: once-through fuel cycle | Statement: [BWR-3, usedFuelCycle, once-through fuel cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFuelCycle Context triple: [BWR-3, usedFuelCycle, once-through fuel cycle]
-
A.
usedFuelCells
Indicates that an entity employed fuel cells as an energy source or power component in its operation or design.
-
B.
usesFuelCycleService
Indicates that an entity relies on or engages a fuel cycle service (such as fuel supply, processing, or management) provided by another entity.
-
C.
fuelCycleType
chosen
Indicates the type or category of fuel cycle process associated with or applied to an entity.
-
D.
typicalFuelCycleLength
Indicates the usual duration of a complete fuel usage and replacement cycle for a system or process.
-
E.
fuelCycleFeature
Indicates a characteristic, attribute, or aspect associated with a nuclear fuel cycle process or stage.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 30, 2026, 11:16 p.m.