Triple
T25002813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee Nuclear Power Plant, South Carolina |
E625762
|
entity |
| Predicate | hasNoAttribute |
P170323
|
FINISHED |
| Object | no nuclear fuel ever loaded |
—
|
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: no nuclear fuel ever loaded | Statement: [Cherokee Nuclear Power Plant, South Carolina, hasNoAttribute, no nuclear fuel ever loaded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoAttribute Context triple: [Cherokee Nuclear Power Plant, South Carolina, hasNoAttribute, no nuclear fuel ever loaded]
-
A.
hasNoText
Indicates that the referenced entity or element contains no textual content.
-
B.
hasNoEffective
Indicates that one entity lacks any effective influence, impact, or valid effect on another entity or condition.
-
C.
holdsAttribute
Indicates that one entity possesses, exhibits, or is characterized by a particular attribute or property.
-
D.
hasNoChildren
Indicates that the subject entity does not have any children associated with it.
-
E.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 18, 2026, 6:05 a.m.