Triple

T21772942
Position Surface form Disambiguated ID Type / Status
Subject Dharani E537480 entity
Predicate maritalStatusInTradition P47938 FINISHED
Object married to Parashurama 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: married to Parashurama | Statement: [Dharani, maritalStatusInTradition, married to Parashurama]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maritalStatusInTradition
Context triple: [Dharani, maritalStatusInTradition, married to Parashurama]
  • A. hasSpouseInTradition
    Indicates that one entity is recognized as the spouse of another according to a specified cultural, religious, or legal tradition.
  • B. maritalStatusInMyth chosen
    Indicates the marital status or relationship state of an entity as portrayed within a specific myth or mythological tradition.
  • C. marriageType
    Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
  • D. spouseTraditionNote
    Indicates a note or comment describing traditional customs, practices, or contextual information related to a person’s spouse relationship.
  • E. marital status
    Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
  • 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f031af6a488190a2dcebed43d199d4 completed April 28, 2026, 4:03 a.m.
PD Predicate disambiguation batch_69e6be6299988190a34c98fa76d94700 completed April 21, 2026, 12:01 a.m.
Created at: April 16, 2026, 6:51 p.m.