Triple
T36869321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cernavodă Nuclear Power Plant |
E911181
|
entity |
| Predicate | commissioningDateUnit1 |
P186604
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Cernavodă Nuclear Power Plant, commissioningDateUnit1, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissioningDateUnit1 Context triple: [Cernavodă Nuclear Power Plant, commissioningDateUnit1, 1996]
-
A.
commissioningYearUnit1
Indicates the time unit (e.g., year, month) used to express the commissioning year of the first unit.
-
B.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
C.
commissioningYearUnit3
Indicates the year in which the third unit of an asset, facility, or system was officially commissioned and put into operation.
-
D.
commissionedAt
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
-
E.
commissioningEndYear
Indicates the calendar year in which the commissioning or initial operational phase of something is completed or ends.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.