Triple
T33078324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paks Nuclear Power Plant |
E846430
|
entity |
| Predicate | usesContainmentType |
P35299
|
FINISHED |
| Object | VVER-440/213 containment system |
—
|
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: VVER-440/213 containment system | Statement: [Paks Nuclear Power Plant, usesContainmentType, VVER-440/213 containment system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesContainmentType Context triple: [Paks Nuclear Power Plant, usesContainmentType, VVER-440/213 containment system]
-
A.
hasContainmentType
chosen
Indicates the specific way in which one entity is contained within or enclosed by another.
-
B.
requiresContainment
Indicates that one entity must be physically or logically enclosed within another entity as a necessary condition or constraint.
-
C.
hasContainment
Indicates that one entity spatially or logically encloses, includes, or holds another within its bounds.
-
D.
usesContainer
Indicates that one entity employs or relies on another entity as a container or holding medium for its contents or components.
-
E.
containsUse
Indicates that one entity includes or makes use of another entity as part of its composition, function, or implementation.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:25 a.m.