Triple
T32369300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krafft point |
E827086
|
entity |
| Predicate | temperatureRegionAbove |
P174459
|
FINISHED |
| Object | surfactant is soluble and forms micelles |
—
|
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: surfactant is soluble and forms micelles | Statement: [Krafft point, temperatureRegionAbove, surfactant is soluble and forms micelles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureRegionAbove Context triple: [Krafft point, temperatureRegionAbove, surfactant is soluble and forms micelles]
-
A.
temperatureRegionBelow
Indicates that the temperature in one region is lower than the temperature in another region.
-
B.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
C.
temperatureConditions
Indicates the specific thermal or weather-related temperature state or range affecting an entity or situation.
-
D.
maximumForGivenTemperatures
Indicates the maximum value attained when considering a specified set or range of temperatures.
-
E.
hasTemperatureCriterion
Indicates that something is associated with a specific temperature-based condition or requirement that must be met.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:50 a.m.