Triple
T17196382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economic Simplified Boiling Water Reactor |
E417360
|
entity |
| Predicate | designCertificationDate |
P2256
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Economic Simplified Boiling Water Reactor, designCertificationDate, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designCertificationDate Context triple: [Economic Simplified Boiling Water Reactor, designCertificationDate, 2014]
-
A.
certificationDate
chosen
Indicates the date on which an entity was officially certified or granted a formal certification.
-
B.
certificationBy
Indicates that one entity formally attests to, approves, or validates the qualifications, standards, or authenticity of another entity.
-
C.
typeOfCertification
Indicates the specific kind or category of certification associated with an entity.
-
D.
isCertified
Indicates that an entity has been officially recognized as meeting specific standards or qualifications by an authorized body.
-
E.
hasCertificationLabel
Indicates that an entity bears or is associated with a specific certification label signifying compliance with defined standards or criteria.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42daab57c819093496cbdc7890f34 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.