Triple
T3881070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvert Cliffs Nuclear Power Plant |
E92822
|
entity |
| Predicate | unit2Commissioned |
P52113
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Calvert Cliffs Nuclear Power Plant, unit2Commissioned, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unit2Commissioned Context triple: [Calvert Cliffs Nuclear Power Plant, unit2Commissioned, 1977]
-
A.
commissionedStatus
Indicates whether an entity has been formally authorized, activated, or placed into official service or duty.
-
B.
commissionedBy
Indicates that one entity has been formally requested, authorized, or hired by another entity to create, perform, or carry out something.
-
C.
commissionedIn
Indicates that an entity was formally requested or authorized to be created, produced, or carried out in a specific time period or location.
-
D.
commissioned
Indicates that one entity formally authorized or ordered another entity to create, produce, or carry out something, often in exchange for payment or obligation.
-
E.
commissionedFor
Indicates that something was formally requested or created to serve a specific purpose, project, or recipient.
- F. None of above. chosen
Provenance (4 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:20 p.m.