Triple
T33943578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Point Energy Center |
E870230
|
entity |
| Predicate | fuelPoolStorage |
P54417
|
FINISHED |
| Object | on-site spent fuel pools |
—
|
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: on-site spent fuel pools | Statement: [Indian Point Energy Center, fuelPoolStorage, on-site spent fuel pools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelPoolStorage Context triple: [Indian Point Energy Center, fuelPoolStorage, on-site spent fuel pools]
-
A.
hasFuelStorage
chosen
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
-
B.
fuelLocation
Indicates the place or source where fuel is stored, supplied, or located for use.
-
C.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
D.
propellantStorage
Indicates that one entity serves as a location or facility where propellant is stored for later use.
-
E.
fuelManagement
Indicates the management, control, or optimization of fuel usage, storage, and distribution within a system or process.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.