Triple
T36869349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cernavodă Nuclear Power Plant |
E911181
|
entity |
| Predicate | lifetimeExtensionPlanned |
P186605
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cernavodă Nuclear Power Plant, lifetimeExtensionPlanned, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeExtensionPlanned Context triple: [Cernavodă Nuclear Power Plant, lifetimeExtensionPlanned, yes]
-
A.
lifetimeExtensionDecision
Indicates a decision has been made to extend the operational lifetime or validity period of an entity beyond its originally planned end date.
-
B.
plannedExtensionLength
Indicates the intended or proposed length of an extension as specified in a plan or design.
-
C.
plannedExtensionTo
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
D.
extendedSupportEndDate
Indicates the date on which an extended support period for something ends.
-
E.
extendedIndefinitelyOn
Indicates that something was prolonged or continued without a specified end point in relation to something else.
- 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.