Triple
T28016067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVER-1000 |
E707547
|
entity |
| Predicate | fuelAssemblyLattice |
P157839
|
FINISHED |
| Object | hexagonal |
—
|
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: hexagonal | Statement: [VVER-1000, fuelAssemblyLattice, hexagonal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelAssemblyLattice Context triple: [VVER-1000, fuelAssemblyLattice, hexagonal]
-
A.
fuelAssemblyType
Indicates the specific design or classification of a fuel assembly associated with an entity.
-
B.
numberOfFuelAssemblies
Indicates the total count of fuel assemblies associated with or contained in a given system, component, or facility.
-
C.
fuelCladding
Indicates a relationship where a material or component serves as the cladding (protective outer layer) for nuclear fuel.
-
D.
controlRodMaterial
Indicates the material from which a control rod is made in a nuclear or control system context.
-
E.
formsLatticeIn
chosen
Indicates that the related elements, under a specified operation or order, collectively constitute a lattice structure within the referenced context or set.
- 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_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. |
Created at: April 27, 2026, 8:06 p.m.