Triple
T33078319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paks Nuclear Power Plant |
E846430
|
entity |
| Predicate | PaksIIReactorSupplier |
P121470
|
FINISHED |
| Object | Rosatom |
—
|
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: Rosatom | Statement: [Paks Nuclear Power Plant, PaksIIReactorSupplier, Rosatom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PaksIIReactorSupplier Context triple: [Paks Nuclear Power Plant, PaksIIReactorSupplier, Rosatom]
-
A.
reactorTechnologySupplier
chosen
Indicates that one entity supplies or provides reactor technology to another entity.
-
B.
hasNuclearReactorType
Indicates that an entity possesses or is equipped with a specific type or classification of nuclear reactor.
-
C.
electricalCapacityPerReactor_MWe
Indicates the electrical power output capacity, measured in megawatts electric (MWe), that is provided by each individual reactor.
-
D.
plannedNumberOfReactors
Indicates the total number of reactors that are intended or scheduled to be built, installed, or operated for a given facility or project.
-
E.
nuclearReactorOrigin
Indicates the source or place from which a nuclear reactor originates or is derived.
- 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_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:25 a.m.