Triple
T36869348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cernavodă Nuclear Power Plant |
E911181
|
entity |
| Predicate | designedLifetimePerUnit_years |
P8105
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Cernavodă Nuclear Power Plant, designedLifetimePerUnit_years, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedLifetimePerUnit_years Context triple: [Cernavodă Nuclear Power Plant, designedLifetimePerUnit_years, 30]
-
A.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
B.
designLifetime
chosen
Indicates the intended duration or operational period for which something is designed to function as specified.
-
C.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
D.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
-
E.
hasLifeSpan
Indicates that an entity is associated with a specific duration or range of time during which it remains alive or exists.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4:13 p.m.