Triple
T36869339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cernavodă Nuclear Power Plant |
E911181
|
entity |
| Predicate | usesReactorModel |
P52112
|
FINISHED |
| Object | CANDU 6 |
—
|
NE NERFINISHED |
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: CANDU 6 | Statement: [Cernavodă Nuclear Power Plant, usesReactorModel, CANDU 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReactorModel Context triple: [Cernavodă Nuclear Power Plant, usesReactorModel, CANDU 6]
-
A.
hasReactorUnit
Indicates that one entity possesses, contains, or is equipped with a specific reactor unit as a component or subsystem.
-
B.
reactorModel
chosen
Indicates a specific reactor design or configuration that an entity is based on, uses, or is associated with.
-
C.
usesModelsType
Indicates that one entity employs or relies on a specific type or category of models in its operation or behavior.
-
D.
usesModalSystem
Indicates that one entity employs or operates within a particular modal system (such as a framework of modes, modalities, or modal logic) in relation to another entity or context.
-
E.
reactor
Indicates a relationship where an entity functions as or is associated with a nuclear or chemical reactor system.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.