Triple
T33078302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paks Nuclear Power Plant |
E846430
|
entity |
| Predicate | commercialOperationUnit1 |
P51665
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Paks Nuclear Power Plant, commercialOperationUnit1, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialOperationUnit1 Context triple: [Paks Nuclear Power Plant, commercialOperationUnit1, 1983]
-
A.
commercialOperationStartUnit2
Indicates the point in time when the second unit of a facility or system begins its commercial operation.
-
B.
commercialOperationStartUnit1
chosen
Indicates the date or time when commercial operation of Unit 1 begins.
-
C.
commercialOperation
Indicates that an entity is engaged in or associated with a profit-oriented business activity or transaction.
-
D.
commercialOperationStartUnit3
Indicates the point in time when the third unit of a facility or system begins its commercial operation.
-
E.
commercialOperationStartUnit4
Indicates the point in time or unit at which the fourth unit of a facility or system begins its commercial operation.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:25 a.m.