Triple
T16238519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combustion Engineering PWR |
E394178
|
entity |
| Predicate | steamGeneratorType |
P90830
|
FINISHED |
| Object | once-through steam generator |
—
|
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 steam generator | Statement: [Combustion Engineering PWR, steamGeneratorType, once-through steam generator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: steamGeneratorType Context triple: [Combustion Engineering PWR, steamGeneratorType, once-through steam generator]
-
A.
steamGenerationMethod
chosen
Indicates the method or process by which steam is produced or generated.
-
B.
boilerType
Indicates the specific kind or category of boiler associated with an entity, such as its design, fuel source, or operating characteristics.
-
C.
heatingMethod
Indicates the method or technique used to apply heat to something, such as for cooking, warming, or processing.
-
D.
turbineType
Indicates the specific kind or category of turbine associated with or used by an entity.
-
E.
hasBoilerPosition
Indicates the spatial placement or designated location of a boiler relative to another object or within a given environment.
- 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.