Triple
T30666829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redcar Steelworks |
E780684
|
entity |
| Predicate | blastFurnaceType |
P171085
|
FINISHED |
| Object | one of the largest blast furnaces in Europe |
—
|
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: one of the largest blast furnaces in Europe | Statement: [Redcar Steelworks, blastFurnaceType, one of the largest blast furnaces in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blastFurnaceType Context triple: [Redcar Steelworks, blastFurnaceType, one of the largest blast furnaces in Europe]
-
A.
blastFurnaceName
Indicates the naming relationship that assigns a specific name to a blast furnace.
-
B.
blastFurnaceCommissioned
Indicates that a blast furnace has been officially put into operation or brought into active service.
-
C.
fuelSourceForSmelting
Indicates that one entity serves as the fuel used to generate heat for smelting another entity.
-
D.
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.
-
E.
coalType
Indicates the specific kind or classification of coal associated with an 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_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:31 p.m.