Triple
T34918785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVER-440 |
E1007077
|
entity |
| Predicate | primaryPressure |
P122284
|
FINISHED |
| Object | about 12.5–12.7 MPa |
—
|
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: about 12.5–12.7 MPa | Statement: [VVER-440, primaryPressure, about 12.5–12.7 MPa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPressure Context triple: [VVER-440, primaryPressure, about 12.5–12.7 MPa]
-
A.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
B.
primarySystemPressure
chosen
Indicates the pressure value present in the main or primary system within a larger setup or process.
-
C.
pressurized
Indicates that one entity exerts or maintains pressure on another, often creating a constrained or high-pressure condition.
-
D.
pressureTransmission
Indicates that pressure applied at one point in a system is conveyed or propagated to another point within that system.
-
E.
pressureFrom
Indicates a relationship where one entity exerts influence, coercion, or force on another to affect its decisions, actions, or state.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.