Triple
T4068871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vogtle Unit 1 |
E86594
|
entity |
| Predicate | gridConnectionDate |
P34483
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Vogtle Unit 1, gridConnectionDate, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridConnectionDate Context triple: [Vogtle Unit 1, gridConnectionDate, 1987]
-
A.
gridConnectionCompletionDate
chosen
Indicates the date on which a connection to the electrical grid is fully completed and becomes operational.
-
B.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
C.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
D.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
E.
electrificationUsedBetween
Indicates that an electrification system or method is applied or present along the segment or connection between two entities.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf8f33c8190a6afca1830f35485 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.