Triple
T17196337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi 3 |
E417359
|
entity |
| Predicate | gridStabilityContribution |
P58869
|
FINISHED |
| Object | voltage and frequency support |
—
|
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: voltage and frequency support | Statement: [Fermi 3, gridStabilityContribution, voltage and frequency support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridStabilityContribution Context triple: [Fermi 3, gridStabilityContribution, voltage and frequency support]
-
A.
gridInterconnection
Indicates a connection or linkage between electrical grids that allows power exchange or coordinated operation.
-
B.
hasGridConnection
Indicates that an entity is connected to an electrical grid, enabling it to receive or supply grid-based power.
-
C.
gridConnectionStatus
Indicates whether and how an entity is currently connected to an electrical or energy distribution grid.
-
D.
electricPowerOutput
Indicates the amount of electrical power produced or delivered by an entity.
-
E.
energyContribution
chosen
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42daab57c819093496cbdc7890f34 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.