Triple
T32934154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal House of Negeri Sembilan |
E842481
|
entity |
| Predicate | hasDynasticStyle |
P119623
|
FINISHED |
| Object | Yang Maha Mulia |
—
|
NE NERFINISHED |
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: Yang Maha Mulia | Statement: [Royal House of Negeri Sembilan, hasDynasticStyle, Yang Maha Mulia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynasticStyle Context triple: [Royal House of Negeri Sembilan, hasDynasticStyle, Yang Maha Mulia]
-
A.
hasDynasticHouseStyle
Indicates that an entity is associated with or characterized by a particular dynastic house’s stylistic tradition or aesthetic.
-
B.
isDynastic
Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
-
C.
hasDynasticFunction
Indicates that something serves a role or purpose within a dynasty, such as supporting its continuity, authority, or internal organization.
-
D.
isMonarchicalStyle
chosen
Indicates that the relationship or action involves having or using a monarchical style, such as a royal or sovereign form of address or title.
-
E.
hasDynast
Indicates that an entity is associated with or ruled by a particular dynasty.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d108f2008190be705c3372b95fe5 |
completed | May 3, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.