Triple
T30666827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redcar Steelworks |
E780684
|
entity |
| Predicate | blastFurnaceName |
P170474
|
FINISHED |
| Object | Redcar blast furnace |
—
|
NE NERFINISHED |
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: Redcar blast furnace | Statement: [Redcar Steelworks, blastFurnaceName, Redcar blast furnace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blastFurnaceName Context triple: [Redcar Steelworks, blastFurnaceName, Redcar blast furnace]
-
A.
blastFurnaceCommissioned
Indicates that a blast furnace has been officially put into operation or brought into active service.
-
B.
fuelSourceForSmelting
Indicates that one entity serves as the fuel used to generate heat for smelting another entity.
-
C.
foundry
Indicates a relationship where an entity operates as or is associated with a foundry, typically involved in casting or producing metal or similar materials.
-
D.
forgedWith
Indicates that something has been created, shaped, or formed through the use of a specified tool, material, method, or collaborative partner.
-
E.
hasSmelterFeed
Indicates that an entity serves as input material or feedstock for a smelting process used by another entity.
- 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_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 29, 2026, 8:31 p.m.