Triple

T36228116
Position Surface form Disambiguated ID Type / Status
Subject Tunku Ali Redhauddin E891161 entity
Predicate familyName P18 FINISHED
Object ibni Tuanku Muhriz
Ibni Tuanku Muhriz is a Malay royal patronymic indicating "son of Tuanku Muhriz," used as part of the names of members of the Negeri Sembilan royal family in Malaysia.
E891161 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: ibni Tuanku Muhriz | Statement: [Tunku Ali Redhauddin, familyName, ibni Tuanku Muhriz]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: ibni Tuanku Muhriz
Triple: [Tunku Ali Redhauddin, familyName, ibni Tuanku Muhriz]
Generated description
Ibni Tuanku Muhriz is a Malay royal patronymic indicating "son of Tuanku Muhriz," used as part of the names of members of the Negeri Sembilan royal family in Malaysia.

Provenance (5 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_69f76e4387048190a1b27bcbf4ec7423 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b5a0d2a48190a32496970ed5f223 completed May 3, 2026, 8:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5ad71b60008190906b4ad76ae76a36 completed July 18, 2026, 1:30 a.m.
NEDg Description generation batch_6a5ad82f2cc48190bd8d8a49a2d410a0 completed July 18, 2026, 1:34 a.m.
NED2 Entity disambiguation (via description) batch_6a5ad886e008819086121eadc086217b completed July 18, 2026, 1:36 a.m.
Created at: May 3, 2026, 4:09 p.m.