Triple
T30392645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CANDU reactor technology |
E773129
|
entity |
| Predicate | pressureVessel |
P169152
|
FINISHED |
| Object | no large single pressure vessel |
—
|
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: no large single pressure vessel | Statement: [CANDU reactor technology, pressureVessel, no large single pressure vessel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureVessel Context triple: [CANDU reactor technology, pressureVessel, no large single pressure vessel]
-
A.
pressureVesselMaterial
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.
pressurizedVolume
Indicates that a specified volume is maintained at a pressure different from ambient (typically higher), often as part of a controlled or sealed system.
-
D.
pressurizedVariant
Indicates that one entity is a pressurized version or configuration of another entity.
-
E.
pressureTransmission
Indicates that pressure applied at one point in a system is conveyed or propagated to another point within that system.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685a6ddb08190a4664c0597e80bf2 |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:02 p.m.