Triple
T32934004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seri Setia Mahkota |
E842477
|
entity |
| Predicate | honorificPrefixConferred |
P141044
|
FINISHED |
| Object | Tun |
—
|
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: Tun | Statement: [Seri Setia Mahkota, honorificPrefixConferred, Tun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificPrefixConferred Context triple: [Seri Setia Mahkota, honorificPrefixConferred, Tun]
-
A.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
B.
honoraryPrefix
Indicates that one entity serves as an honorific title or respectful prefix attached to the name of another entity.
-
C.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
D.
confersHonorificStatus
chosen
Indicates that one entity formally grants an honorific title, rank, or status to another entity.
-
E.
honorificTitleGivenBy
Indicates that an honorific title is formally conferred on one entity by another entity.
- 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_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:20 a.m.