Triple

T10576902
Position Surface form Disambiguated ID Type / Status
Subject Trishala E249632 entity
Predicate dreamsInterpretedBy P52291 FINISHED
Object royal priests (according to Jain texts) 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: royal priests (according to Jain texts) | Statement: [Trishala, dreamsInterpretedBy, royal priests (according to Jain texts)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dreamsInterpretedBy
Context triple: [Trishala, dreamsInterpretedBy, royal priests (according to Jain texts)]
  • A. interpretedDreamFor chosen
    Indicates that one entity has provided an explanation or analysis of the meaning of another entity’s dream.
  • B. starMeaning
    Indicates that one entity represents or conveys the symbolic or interpretive significance of a star associated with another entity.
  • C. hasDreamingBeliefs
    Indicates that an entity holds beliefs, views, or assumptions specifically about dreams or the nature of dreaming.
  • D. associatedNightMeaning
    Indicates a relationship where something is linked to, characterized by, or symbolically connected with a particular meaning that is specifically tied to the night.
  • E. dream
    Indicates that an entity experiences or has a dream involving another entity or concept.
  • 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_69d381c8bd708190acf3d275c908251e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5275628988190bd00dd3f8d7c3937 completed April 7, 2026, 3:48 p.m.
PD Predicate disambiguation batch_69d51901ff6c819095e7b528170a69dc completed April 7, 2026, 2:47 p.m.
Created at: April 6, 2026, 12:38 p.m.