Triple
T30666832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redcar Steelworks |
E780684
|
entity |
| Predicate | blastFurnaceBlownOut |
P171303
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Redcar Steelworks, blastFurnaceBlownOut, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blastFurnaceBlownOut Context triple: [Redcar Steelworks, blastFurnaceBlownOut, 2015]
-
A.
blastFurnaceType
Indicates that one entity is a blast furnace and the other specifies its particular type or classification.
-
B.
blastFurnaceName
Indicates the naming relationship that assigns a specific name to a blast furnace.
-
C.
blastFurnaceCommissioned
Indicates that a blast furnace has been officially put into operation or brought into active service.
-
D.
laterBlownUpTo
Indicates that one entity is subsequently destroyed or blown up at a later time relative to another referenced event or state.
-
E.
smelterClosed
Indicates that a smelting facility has ceased operations, either temporarily or permanently.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 8:31 p.m.