Triple
T15131233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borssele nuclear power plant |
E361423
|
entity |
| Predicate | usesFuelCycleService |
P117439
|
FINISHED |
| Object | enrichment abroad |
—
|
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: enrichment abroad | Statement: [Borssele nuclear power plant, usesFuelCycleService, enrichment abroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFuelCycleService Context triple: [Borssele nuclear power plant, usesFuelCycleService, enrichment abroad]
-
A.
fuelCycleFeature
Indicates a characteristic, attribute, or aspect associated with a nuclear fuel cycle process or stage.
-
B.
usedFuelCells
Indicates that an entity employed fuel cells as an energy source or power component in its operation or design.
-
C.
hasFuelServices
Indicates that one entity provides or is equipped with fuel-related services or facilities for another entity.
-
D.
usedFusionFuel
Indicates that an entity employed a specified material or substance as fuel in a fusion process.
-
E.
hasRefuelingSystemSupplier
Indicates that one entity serves as the supplier or provider of the refueling system for another entity.
- F. None of above. chosen
Provenance (4 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:06 a.m.