Triple
T18603667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Temperate Zone |
E454682
|
entity |
| Predicate | hasGeneralTemperatureRange |
P100818
|
FINISHED |
| Object | mild to cool |
—
|
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: mild to cool | Statement: [South Temperate Zone, hasGeneralTemperatureRange, mild to cool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralTemperatureRange Context triple: [South Temperate Zone, hasGeneralTemperatureRange, mild to cool]
-
A.
temperatureRangeVariant
Indicates a relationship where one temperature range is a variation or alternative form of another temperature range.
-
B.
hasTemperatureRegime
Indicates that an entity is characterized by or associated with a particular pattern or regime of temperature conditions.
-
C.
humidityRange
Indicates the range of humidity values within which a condition, process, or entity is defined, operates, or remains valid.
-
D.
hasTemperatureCategory
chosen
Indicates that an entity is associated with a specific qualitative temperature classification (e.g., hot, cold, warm).
-
E.
growthTemperatureRange
Indicates the range of temperatures within which an organism or entity can grow or function effectively.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54752abec8190a5f4aa84abe8b240 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.