Triple

T17962225
Position Surface form Disambiguated ID Type / Status
Subject Varsha E449112 entity
Predicate follows P134 FINISHED
Object Grishma NE NERFINISHED

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: Grishma | Statement: [Varsha, follows, Grishma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grishma
Context triple: [Varsha, follows, Grishma]
  • A. Grishma chosen
    Grishma is the hot summer season in the Hindu lunisolar calendar, typically associated with intense heat and dry weather.
  • B. Dhurwa
    Dhurwa is an indigenous tribal community of central India, primarily found in Chhattisgarh and neighboring regions, known for its distinct Dravidian language and cultural traditions.
  • C. Varsha
    Varsha is the monsoon season in the Hindu lunisolar calendar, marked by heavy rains and agricultural renewal.
  • D. Shivini
    Shivini is the Urartian sun god, often associated with light, justice, and royal authority in the ancient Kingdom of Urartu.
  • E. Bhadrika
    Bhadrika is a disciple mentioned in Buddhist tradition as one of the listeners present when the Buddha delivered his seminal Turning of the Wheel of Dharma discourse.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4b134bc68819097cc199ea8e80f6c completed April 19, 2026, 10:40 a.m.
Created at: April 10, 2026, 10:22 a.m.