Triple

T19429764
Position Surface form Disambiguated ID Type / Status
Subject Köppen BSk E486079 entity
Predicate hasGeneralCondition P72526 FINISHED
Object generally dry conditions 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: generally dry conditions | Statement: [Köppen BSk, hasGeneralCondition, generally dry conditions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGeneralCondition
Context triple: [Köppen BSk, hasGeneralCondition, generally dry conditions]
  • A. hasTypicalConditions chosen
    Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
  • B. hasNaturalCondition
    Indicates that an entity possesses or is subject to a particular natural state, feature, or condition inherent to its environment or biology.
  • C. globalCondition
    Indicates that a condition applies universally or system-wide rather than being limited to a specific local context or subset.
  • D. hasCondition
    Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
  • E. hasMoreChallengingConditionsIn
    Indicates that one situation, environment, or context involves stricter, harsher, or more demanding conditions than another within a specified domain.
  • 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6321c774881908ba5bde20abd5adc completed April 20, 2026, 2:03 p.m.
PD Predicate disambiguation batch_69e4fd6e806081909053f325ba01ab6b completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:37 p.m.