Triple
T34433792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claus process |
E883896
|
entity |
| Predicate | catalyticStageTemperatureRange |
P3958
|
FINISHED |
| Object | 200–350 °C |
—
|
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: 200–350 °C | Statement: [Claus process, catalyticStageTemperatureRange, 200–350 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalyticStageTemperatureRange Context triple: [Claus process, catalyticStageTemperatureRange, 200–350 °C]
-
A.
productionTemperature
Indicates the temperature at which a product, material, or substance is produced or processed.
-
B.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
-
C.
operatingTemperature
chosen
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
D.
growthTemperatureRange
Indicates the range of temperatures within which an organism or entity can grow or function effectively.
-
E.
heatOutputRange
Indicates the range of heat energy or thermal power that an entity can produce or emit under specified conditions.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2 a.m.