Triple
T10756889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | triple-alpha process |
E253718
|
entity |
| Predicate | temperatureThreshold |
P4459
|
FINISHED |
| Object | about 10^8 K |
—
|
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: about 10^8 K | Statement: [triple-alpha process, temperatureThreshold, about 10^8 K]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureThreshold Context triple: [triple-alpha process, temperatureThreshold, about 10^8 K]
-
A.
hasTemperature
chosen
Indicates that an entity possesses or is characterized by a specific temperature value.
-
B.
temperatureChange
Indicates a change in temperature between two states, times, or conditions, specifying how much and in which direction the temperature has varied.
-
C.
humidityRange
Indicates the range of humidity values within which a condition, process, or entity is defined, operates, or remains valid.
-
D.
temperatureRangeDifference
Indicates the difference between two temperature ranges, typically measuring how much one range is higher or lower than another.
-
E.
temperatureProportionalTo
Indicates that the temperature of one entity changes in direct proportion to the temperature of another 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d72e9fded88190940df48344fc368e |
completed | April 9, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.