Triple
T18751073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shippingport Atomic Power Station |
E458525
|
entity |
| Predicate | laterCoreDesign |
P133407
|
FINISHED |
| Object | light water breeder reactor core |
—
|
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: light water breeder reactor core | Statement: [Shippingport Atomic Power Station, laterCoreDesign, light water breeder reactor core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCoreDesign Context triple: [Shippingport Atomic Power Station, laterCoreDesign, light water breeder reactor core]
-
A.
laterConstruction
Indicates that one construction event or structure occurred or was built after another in time.
-
B.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
C.
laterDeveloper
Indicates that one developer’s work, role, or involvement occurs after another developer in time.
-
D.
laterDevelopments
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
E.
laterProduction
Indicates that one production event or version occurs after another in time.
- F. None of above. chosen
Provenance (4 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ed4e6881908791f2a6250010a6 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:51 a.m.