Triple
T18751049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shippingport Atomic Power Station |
E458525
|
entity |
| Predicate | connectedToGridDate |
P34483
|
FINISHED |
| Object | 1957-12-18 |
—
|
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: 1957-12-18 | Statement: [Shippingport Atomic Power Station, connectedToGridDate, 1957-12-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToGridDate Context triple: [Shippingport Atomic Power Station, connectedToGridDate, 1957-12-18]
-
A.
gridConnectionCompletionDate
chosen
Indicates the date on which a connection to the electrical grid is fully completed and becomes operational.
-
B.
hasGridConnection
Indicates that an entity is connected to an electrical grid, enabling it to receive or supply grid-based power.
-
C.
gridConnectionPlannedFor
Indicates that a future or intended connection to an electrical (or utility) grid is planned for the referenced entity.
-
D.
gridConnectionStatus
Indicates whether and how an entity is currently connected to an electrical or energy distribution grid.
-
E.
partOfNetworkSince
Indicates that an entity has been a member or component of a particular network starting from a specified point in time.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ed4e6881908791f2a6250010a6 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.