Triple

T36228113
Position Surface form Disambiguated ID Type / Status
Subject Tunku Ali Redhauddin E891161 entity
Predicate instanceOf P0 FINISHED
Object member of the Negeri Sembilan royal family C63539 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: member of the Negeri Sembilan royal family
Context triple: [Tunku Ali Redhauddin, instanceOf, member of the Negeri Sembilan royal family]
  • A. member of Thai royal family
    A member of the Thai royal family is an individual who belongs by birth or marriage to the monarchy of Thailand, holding a recognized royal title and status under Thai royal and constitutional traditions.
  • B. Malaysian prince chosen
    A Malaysian prince is a male member of Malaysia’s royal families who holds hereditary or appointed noble status, often performing ceremonial, cultural, and advisory roles within the country’s constitutional monarchy.
  • C. member of Rajagopalachari family
    A member of the Rajagopalachari family is an individual who is biologically descended from, or legally adopted into, the lineage of Indian statesman C. Rajagopalachari and his close relatives.
  • D. Asaf Jahi dynasty member
    A member of the Asaf Jahi dynasty is an individual belonging to the royal family that ruled the princely state of Hyderabad in India from the early 18th to the mid-20th century.
  • E. member of extended royal family
    A member of the extended royal family is an individual related by blood, marriage, or adoption to the reigning monarch or core royal line, but who holds a more distant position in the line of succession and typically fewer official duties.
  • F. None of above.

Provenance (1 batch)

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_69f76e4387048190a1b27bcbf4ec7423 completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:09 p.m.