Triple
T31713105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWR-3 |
E809379
|
entity |
| Predicate | reactorVesselMaterial |
P165114
|
FINISHED |
| Object | low-alloy steel with stainless steel cladding |
—
|
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: low-alloy steel with stainless steel cladding | Statement: [BWR-3, reactorVesselMaterial, low-alloy steel with stainless steel cladding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorVesselMaterial Context triple: [BWR-3, reactorVesselMaterial, low-alloy steel with stainless steel cladding]
-
A.
pressureVesselMaterial
chosen
Indicates that a specified material is used as the construction material for a pressure vessel.
-
B.
reactorVesselPressure
Indicates the pressure exerted by the contents within a reactor vessel during its operation.
-
C.
vacuumVesselMaterial
Indicates that one entity is the material from which the vacuum vessel of another entity is made.
-
D.
controlRodMaterial
Indicates the material from which a control rod is made in a nuclear or control system context.
-
E.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
- 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_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 11:16 p.m.