Triple
T30712037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selangor Sultanate |
E781920
|
entity |
| Predicate | notableSultan |
P140617
|
FINISHED |
| Object | Sultan Abdul Samad |
E900136
|
NE 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: Sultan Abdul Samad | Statement: [Selangor Sultanate, notableSultan, Sultan Abdul Samad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSultan Context triple: [Selangor Sultanate, notableSultan, Sultan Abdul Samad]
-
A.
notableSultanate
Indicates that a sultanate holds particular historical, political, or cultural significance compared to other sultanates.
-
B.
associatedSultan
chosen
Indicates that one entity is linked or connected to a particular sultan in some relevant context or relationship.
-
C.
recognizedAsSultan
Indicates that an entity is acknowledged or accepted by others as holding the status or title of sultan.
-
D.
reignAsValideSultanFor
Indicates that one entity serves and exercises authority as the valide sultan (queen mother) during the reign of another entity, typically a ruling sultan.
-
E.
notableSafavidRuler
Indicates that a person held a historically significant ruling position within the Safavid dynasty.
- F. None of above.
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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3704765f208190a18f228355529365 |
completed | June 20, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:35 p.m.