Triple
T16384985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWR-4 |
E397896
|
entity |
| Predicate | typicalFuelCycleLength |
P123193
|
FINISHED |
| Object | about 18 to 24 months |
—
|
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: about 18 to 24 months | Statement: [BWR-4, typicalFuelCycleLength, about 18 to 24 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFuelCycleLength Context triple: [BWR-4, typicalFuelCycleLength, about 18 to 24 months]
-
A.
fuelCycleFeature
Indicates a characteristic, attribute, or aspect associated with a nuclear fuel cycle process or stage.
-
B.
typicalNumberOfCycles
Indicates the usual or characteristic count of cycles associated with an entity, process, or event.
-
C.
usesFuelCycleService
Indicates that an entity relies on or engages a fuel cycle service (such as fuel supply, processing, or management) provided by another entity.
-
D.
operatingCycle
Indicates the duration or process through which an entity completes a full sequence of its operations from start to finish.
-
E.
typicalFuel
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263c60088190b85a8c02bc3ef315 |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.