Triple
T110422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | open-hearth process |
E2235
|
entity |
| Predicate | combustionSystem |
P840
|
FINISHED |
| Object | regenerative burner system |
—
|
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: regenerative burner system | Statement: [open-hearth process, combustionSystem, regenerative burner system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combustionSystem Context triple: [open-hearth process, combustionSystem, regenerative burner system]
-
A.
partOfSystem
chosen
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
B.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
C.
fueledBy
Indicates that one entity provides the energy or power source that enables the operation or functioning of another entity.
-
D.
typicalEngine
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
E.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.