Triple
T32506437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Sultan Alauddin Riayat Shah VI |
E830808
|
entity |
| Predicate | usesRoyalInsigniaType |
P162086
|
FINISHED |
| Object | Malay royal regalia |
—
|
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: Malay royal regalia | Statement: [House of Sultan Alauddin Riayat Shah VI, usesRoyalInsigniaType, Malay royal regalia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoyalInsigniaType Context triple: [House of Sultan Alauddin Riayat Shah VI, usesRoyalInsigniaType, Malay royal regalia]
-
A.
hasRoyalSymbol
chosen
Indicates that an entity possesses or is associated with a symbol representing royalty or royal authority.
-
B.
hasRoyalWarrantFrom
Indicates that one party has been formally granted a royal warrant or official endorsement by a specific royal person or household.
-
C.
royalStandard
Indicates that an entity is the official royal flag or emblem used to represent a monarch or royal authority.
-
D.
hasInescutcheon
Indicates that one heraldic shield or coat of arms bears another smaller shield (an inescutcheon) placed upon it.
-
E.
hasHeraldicUse
Indicates that something is used as, or incorporated into, a heraldic device, emblem, or coat of arms.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1 a.m.