Triple
T4837118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guna |
E108085
|
entity |
| Predicate | monsoonCharacteristics |
P14881
|
FINISHED |
| Object | seasonal monsoon rainfall |
—
|
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: seasonal monsoon rainfall | Statement: [Guna, monsoonCharacteristics, seasonal monsoon rainfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monsoonCharacteristics Context triple: [Guna, monsoonCharacteristics, seasonal monsoon rainfall]
-
A.
primaryRainySeasonFor
Indicates that one entity is the main or most significant rainy season associated with a particular place or region.
-
B.
hasExtremeWeatherCharacteristic
Indicates that something possesses a notable or defining feature related to extreme weather conditions.
-
C.
seasonCharacterization
chosen
Indicates how a particular season is described, defined, or characterized in terms of its qualities or attributes.
-
D.
KhareefSeasonOccursIn
Indicates that a khareef (monsoon) season takes place within a specified geographic location or region.
-
E.
drySeason
Indicates that the relationship or action occurs during, or is characteristic of, a period with little or no rainfall.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.