Triple
T30950365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Salehuddin Shah |
E788521
|
entity |
| Predicate | hasMonarchicalOrder |
P194367
|
FINISHED |
| Object | first Sultan of Selangor |
—
|
LITERAL 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: first Sultan of Selangor | Statement: [Sultan Salehuddin Shah, hasMonarchicalOrder, first Sultan of Selangor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonarchicalOrder Context triple: [Sultan Salehuddin Shah, hasMonarchicalOrder, first Sultan of Selangor]
-
A.
hasDynasticOrder
Indicates that there exists a specific sequence or hierarchy of dynasties or ruling lines associated with the subject.
-
B.
isMonarchicalStyle
Indicates that the relationship or action involves having or using a monarchical style, such as a royal or sovereign form of address or title.
-
C.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
D.
monarchicRank
Indicates the hierarchical level or status an individual holds within a monarchical system of rule.
-
E.
monarchyEstablished
Indicates that a monarchical form of government has been formally created or instituted for a given entity or territory.
- F. None of above. chosen
Provenance (4 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: April 29, 2026, 8:53 p.m.