Triple
T13933745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chernobyl Nuclear Power Plant |
E335055
|
entity |
| Predicate | gridConnectionEndDate |
P34483
|
FINISHED |
| Object | 2000-12-15 |
—
|
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: 2000-12-15 | Statement: [Chernobyl Nuclear Power Plant, gridConnectionEndDate, 2000-12-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridConnectionEndDate Context triple: [Chernobyl Nuclear Power Plant, gridConnectionEndDate, 2000-12-15]
-
A.
gridConnectionCompletionDate
chosen
Indicates the date on which a connection to the electrical grid is fully completed and becomes operational.
-
B.
gridConnectionAgreementWith
Indicates an agreement establishing the terms and conditions under which one party is connected to another party’s electrical grid.
-
C.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
D.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
E.
gridConnectionPurpose
Indicates the intended role or function of a connection to an electrical grid within a system or network.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf28df081908d897d7b9ec7939d |
completed | April 14, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:17 p.m.