Triple
T28016275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalinin-1 |
E707551
|
entity |
| Predicate | fuelCycleType |
P163628
|
FINISHED |
| Object | once-through |
—
|
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 | Statement: [Kalinin-1, fuelCycleType, once-through]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelCycleType Context triple: [Kalinin-1, fuelCycleType, once-through]
-
A.
fuelCycleFeature
Indicates a characteristic, attribute, or aspect associated with a nuclear fuel cycle process or stage.
-
B.
fuelCycleRole
Indicates the specific function or responsibility an entity has within the nuclear fuel cycle process.
-
C.
typicalFuelCycleLength
Indicates the usual duration of a complete fuel usage and replacement cycle for a system or process.
-
D.
hasFuelCycleCapability
Indicates that an entity possesses the technical and operational ability to carry out one or more stages of the nuclear fuel cycle (such as fuel production, use, or reprocessing).
-
E.
propulsionCycle
Indicates the type or pattern of propulsion operation or cycle that characterizes how a system generates and sustains thrust or movement.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c0796288190a5936b67d90abd00 |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:07 p.m.