Triple
T18751055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shippingport Atomic Power Station |
E458525
|
entity |
| Predicate | thermalReactor |
P90825
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shippingport Atomic Power Station, thermalReactor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalReactor Context triple: [Shippingport Atomic Power Station, thermalReactor, true]
-
A.
thermalNeutronReactor
chosen
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
-
B.
thermalCapacityPerReactor_MWth
Indicates the amount of thermal power capacity, measured in megawatts thermal (MWth), associated with each individual reactor.
-
C.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
D.
nuclearReactorOrigin
Indicates the source or place from which a nuclear reactor originates or is derived.
-
E.
thermalComplex
Indicates a relationship where entities are associated through a thermal interaction, structure, or system forming a combined thermal complex.
- 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_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. |
Created at: April 10, 2026, 11:51 a.m.