Triple
T36869328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cernavodă Nuclear Power Plant |
E911181
|
entity |
| Predicate | statusUnit1 |
P127
|
FINISHED |
| Object | operational |
—
|
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: operational | Statement: [Cernavodă Nuclear Power Plant, statusUnit1, operational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusUnit1 Context triple: [Cernavodă Nuclear Power Plant, statusUnit1, operational]
-
A.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
B.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
C.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
E.
statusSymbol
Indicates that something serves as a marker or representation of an entity’s social, economic, or cultural standing relative to others.
- 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_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: May 3, 2026, 4:13 p.m.