Triple
T28016080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVER-1000 |
E707547
|
entity |
| Predicate | gridConnectionUse |
P90839
|
FINISHED |
| Object | commercial electricity generation |
—
|
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: commercial electricity generation | Statement: [VVER-1000, gridConnectionUse, commercial electricity generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridConnectionUse Context triple: [VVER-1000, gridConnectionUse, commercial electricity generation]
-
A.
gridConnectionStatus
Indicates whether and how an entity is currently connected to an electrical or energy distribution grid.
-
B.
gridConnectionPurpose
chosen
Indicates the intended role or function of a connection to an electrical grid within a system or network.
-
C.
hasGridConnection
Indicates that an entity is connected to an electrical grid, enabling it to receive or supply grid-based power.
-
D.
gridConnectionAgreementWith
Indicates an agreement establishing the terms and conditions under which one party is connected to another party’s electrical grid.
-
E.
gridConnectionPlannedFor
Indicates that a future or intended connection to an electrical (or utility) grid is planned for the referenced entity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c0796288190a5936b67d90abd00 |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:06 p.m.