Triple
T7744849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Anna Nuclear Generating Station |
E175600
|
entity |
| Predicate | hasSpentFuelPool |
P54417
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [North Anna Nuclear Generating Station, hasSpentFuelPool, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpentFuelPool Context triple: [North Anna Nuclear Generating Station, hasSpentFuelPool, yes]
-
A.
hasFuel
Indicates that an entity possesses or contains fuel available for use.
-
B.
hasBurnUnit
Indicates that one entity (typically a medical facility) includes or is equipped with a specialized unit dedicated to the treatment and care of burn patients.
-
C.
hasFuelStorage
chosen
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
-
D.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
E.
hasFuelEnrichmentRange
Indicates that there is a specified range of fuel enrichment levels associated with an entity or relationship.
- 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:07 p.m.