Triple
T10133759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heysham 1 nuclear power station |
E226802
|
entity |
| Predicate | secondaryCircuit |
P92157
|
FINISHED |
| Object | steam cycle |
—
|
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: steam cycle | Statement: [Heysham 1 nuclear power station, secondaryCircuit, steam cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryCircuit Context triple: [Heysham 1 nuclear power station, secondaryCircuit, steam cycle]
-
A.
secondCircuitHolding
Indicates a legal holding or decision issued by the United States Court of Appeals for the Second Circuit.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
D.
secondaryTransmissionRoute
Indicates a non-primary pathway or mechanism through which something (such as a disease, signal, or influence) is transmitted from one entity to another.
-
E.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd33808048190b6023a6cd83fc179 |
completed | April 2, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:06 p.m.