Triple
T10342745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Salahuddin Abdul Aziz Shah |
E243665
|
entity |
| Predicate | reignAsSultanOfSelangorEnd |
P87054
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Sultan Salahuddin Abdul Aziz Shah, reignAsSultanOfSelangorEnd, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsSultanOfSelangorEnd Context triple: [Sultan Salahuddin Abdul Aziz Shah, reignAsSultanOfSelangorEnd, 2001]
-
A.
reignAsRajaPermaisuriAgongStart
Indicates the time at which an individual begins their tenure serving as the Raja Permaisuri Agong (Queen Consort) of Malaysia.
-
B.
recognizedAsSultan
Indicates that an entity is acknowledged or accepted by others as holding the status or title of sultan.
-
C.
successorAsYangDiPertuanBesarOfNegeriSembilan
Indicates that one individual becomes the next Yang di-Pertuan Besar (ruler) of Negeri Sembilan after another individual.
-
D.
reignAsEmirEnd
chosen
Indicates the point in time or event at which an individual's tenure or rule as an emir comes to an end.
-
E.
reignAsYangDiPertuanBesarStart
Indicates the time at which an individual begins their tenure serving as the Yang di-Pertuan Besar.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:55 a.m.