Triple
T247300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thar Desert |
E5064
|
entity |
| Predicate | hasTemperatureCharacteristic |
P274
|
FINISHED |
| Object | very hot summers |
—
|
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: very hot summers | Statement: [Thar Desert, hasTemperatureCharacteristic, very hot summers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemperatureCharacteristic Context triple: [Thar Desert, hasTemperatureCharacteristic, very hot summers]
-
A.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
B.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
C.
coreTemperature
Indicates that an entity has a specific internal or central temperature value.
-
D.
recordedTemperatureRegion
Indicates that a particular temperature measurement was recorded for or associated with a specific geographic region.
-
E.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d13b8088190a3f48f0388d57496 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.