Triple
T7744852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Anna Nuclear Generating Station |
E175600
|
entity |
| Predicate | statusOfUnits1and2 |
P35303
|
FINISHED |
| Object | operational |
—
|
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: operational | Statement: [North Anna Nuclear Generating Station, statusOfUnits1and2, operational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfUnits1and2 Context triple: [North Anna Nuclear Generating Station, statusOfUnits1and2, operational]
-
A.
hasUnitStatus
chosen
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
B.
statusOfSubunit
Indicates the current condition, state, or operational situation of a component or subunit in relation to its larger whole.
-
C.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
D.
statusOfUnion
Indicates the current legal or formal state of a union or partnership between entities.
-
E.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
- 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.