Triple
T19023898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tun |
E465556
|
entity |
| Predicate | hasTitleHolders |
P113994
|
FINISHED |
| Object | former prime ministers of Malaysia |
—
|
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: former prime ministers of Malaysia | Statement: [Tun, hasTitleHolders, former prime ministers of Malaysia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleHolders Context triple: [Tun, hasTitleHolders, former prime ministers of Malaysia]
-
A.
titleHolders
chosen
Indicates that one or more entities currently or formerly hold a specified title, position, or honor.
-
B.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
C.
titleHoldersWere
Indicates that certain entities previously held a specified title or position during a past period.
-
D.
titleHoldersCollectively
Indicates that a group of entities jointly hold, share, or possess a particular title or set of titles as a collective.
-
E.
includedTitleHolder
Indicates that an entity is recognized or recorded as holding a specified title within a given context or collection.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6e166088190937ef19739437f7c |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.