Triple
T16238517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combustion Engineering PWR |
E394178
|
entity |
| Predicate | typicalFuelEnrichment |
P54129
|
FINISHED |
| Object | 2–5 percent U-235 |
—
|
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: 2–5 percent U-235 | Statement: [Combustion Engineering PWR, typicalFuelEnrichment, 2–5 percent U-235]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFuelEnrichment Context triple: [Combustion Engineering PWR, typicalFuelEnrichment, 2–5 percent U-235]
-
A.
hasFuelEnrichmentRange
chosen
Indicates that there is a specified range of fuel enrichment levels associated with an entity or relationship.
-
B.
fuelEnrichment
Indicates the degree to which a fuel has been processed to increase the concentration of its active or fissile component relative to its natural state.
-
C.
typicalFuel
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
-
D.
fuelCladding
Indicates a relationship where a material or component serves as the cladding (protective outer layer) for nuclear fuel.
-
E.
fuelFraction
Indicates the proportion of an object's total mass or capacity that consists of fuel.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455c7a3c81909e3b42edf03be43e |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.