Triple
T31562591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippsburg Nuclear Power Plant |
E805309
|
entity |
| Predicate | reactorSupplier_Philippsburg2 |
P121470
|
FINISHED |
| Object | Kraftwerk Union AG |
—
|
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: Kraftwerk Union AG | Statement: [Philippsburg Nuclear Power Plant, reactorSupplier_Philippsburg2, Kraftwerk Union AG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorSupplier_Philippsburg2 Context triple: [Philippsburg Nuclear Power Plant, reactorSupplier_Philippsburg2, Kraftwerk Union AG]
-
A.
reactorNetCapacity_Philippsburg2
Indicates the net electrical generation capacity of the Philippsburg 2 nuclear reactor.
-
B.
reactorTechnologySupplier
chosen
Indicates that one entity supplies or provides reactor technology to another entity.
-
C.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
-
D.
reactor
Indicates a relationship where an entity functions as or is associated with a nuclear or chemical reactor system.
-
E.
supplyPort
Indicates that one entity serves as a source or interface through which resources, materials, or energy are provided to another entity.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 10:16 p.m.