Triple
T16484276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flamanville 3 nuclear power plant |
E400397
|
entity |
| Predicate | numberOfReactorUnits |
P34726
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Flamanville 3 nuclear power plant, numberOfReactorUnits, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfReactorUnits Context triple: [Flamanville 3 nuclear power plant, numberOfReactorUnits, 1]
-
A.
numberOfReactors
chosen
Indicates the quantity of reactors associated with or contained by a given entity.
-
B.
plannedNumberOfReactors
Indicates the total number of reactors that are intended or scheduled to be built, installed, or operated for a given facility or project.
-
C.
nrcReactorUnitNumber
Indicates the specific unit number assigned to a nuclear reactor within an NRC-licensed facility.
-
D.
numberOfFuelAssemblies
Indicates the total count of fuel assemblies associated with or contained in a given system, component, or facility.
-
E.
nuclearPowerStationUnit
Indicates a relationship where an individual unit (such as a reactor or generating block) is part of or belongs to a specific nuclear power station.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e05bf448190947b9da15fd29d0a |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.