Triple
T32933718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raja Yong Sofia |
E842468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Perak royal family |
C11665
|
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 Perak royal family Context triple: [Raja Yong Sofia, instanceOf, member of the Perak 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.
member of a royal family
chosen
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
-
C.
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.
-
D.
member of a former royal family
A member of a former royal family is an individual descended from or previously holding status within a monarchy that has since lost its ruling power or official political authority.
-
E.
Monarch of Negeri Sembilan
The Monarch of Negeri Sembilan is the hereditary ruler and constitutional head of state of the Malaysian state of Negeri Sembilan, traditionally selected from among the ruling chiefs (Undangs) according to local adat (customary law).
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.