Triple

T9119268
Position Surface form Disambiguated ID Type / Status
Subject Sanjna E218802 entity
Predicate father P120 FINISHED
Object Vishvakarma E496066 NE 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: Vishvakarma | Statement: [Sanjna, father, Vishvakarma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vishvakarma
Context triple: [Sanjna, father, Vishvakarma]
  • A. divine architect Vishvakarma chosen
    Vishvakarma is the divine architect and craftsman of the gods in Hindu mythology, revered as the celestial engineer who designs and constructs heavenly cities, weapons, and palaces.
  • B. Daksha
    Daksha was a ruler who succeeded King Balitung in the line of Mataram (Medang) monarchs in early medieval Java.
  • C. Jamadagni
    Jamadagni is a revered sage in Hindu mythology, best known as one of the Saptarishi and a prominent figure in the legends surrounding his son Parashurama.
  • D. Bharadwaja
    Bharadwaja is an ancient Vedic sage (rishi) revered in Hindu tradition, known as a progenitor of the Bharadwaja gotra and as a prominent seer associated with several hymns of the Rigveda.
  • E. Chitragupta
    Chitragupta is a Hindu deity who serves as the divine scribe and accountant of human deeds, assisting Yamaraja in judging souls after death.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca83dddd548190983b96c664f7f367 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8a7c6d48190a015efd17a017ca1 completed April 1, 2026, 5:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d047baf5e48190aab0eb19908fabfc completed April 3, 2026, 11:05 p.m.
Created at: March 30, 2026, 7:17 p.m.