Triple
T30854569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen Cfa |
E785883
|
entity |
| Predicate | hasTypicalHumidity |
P74279
|
FINISHED |
| Object | high humidity in summer |
—
|
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: high humidity in summer | Statement: [Köppen Cfa, hasTypicalHumidity, high humidity in summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalHumidity Context triple: [Köppen Cfa, hasTypicalHumidity, high humidity in summer]
-
A.
hasHumidity
chosen
Indicates that one entity possesses, exhibits, or is characterized by a certain level or measure of humidity.
-
B.
preferredHumidity
Indicates the level or range of humidity that is most suitable or favored by a given entity.
-
C.
effectOnHumidity
Indicates how one factor or process changes or influences the level of humidity.
-
D.
typicalMoistureContent
Indicates the usual or characteristic amount of moisture present in or associated with an entity under normal conditions.
-
E.
humidityRange
Indicates the range of humidity values within which a condition, process, or entity is defined, operates, or remains valid.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 29, 2026, 8:46 p.m.