Triple
T34433791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claus process |
E883896
|
entity |
| Predicate | thermalStageTemperatureRange |
P170618
|
FINISHED |
| Object | 1000–1400 °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: 1000–1400 °C | Statement: [Claus process, thermalStageTemperatureRange, 1000–1400 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalStageTemperatureRange Context triple: [Claus process, thermalStageTemperatureRange, 1000–1400 °C]
-
A.
growthTemperatureRange
Indicates the range of temperatures within which an organism or entity can grow or function effectively.
-
B.
temperatureRangeVariant
Indicates a relationship where one temperature range is a variation or alternative form of another temperature range.
-
C.
surfaceTemperatureRange
Indicates the range between the minimum and maximum surface temperatures observed or allowed for an entity.
-
D.
heatOutputRange
Indicates the range of heat energy or thermal power that an entity can produce or emit under specified conditions.
-
E.
productionTemperature
chosen
Indicates the temperature at which a product, material, or substance is produced or processed.
- 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_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.