Triple
T37063223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Malaya |
E917375
|
entity |
| Predicate | thirdHolderStart |
P193029
|
FINISHED |
| Object | 1960-09-21 |
—
|
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: 1960-09-21 | Statement: [King of Malaya, thirdHolderStart, 1960-09-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdHolderStart Context triple: [King of Malaya, thirdHolderStart, 1960-09-21]
-
A.
thirdHolder
Indicates that an entity serves as the third holder or possessor of another entity in a sequence or ordered set of holders.
-
B.
subsequentHolder
Indicates that one entity becomes the next holder or possessor of something after another entity.
-
C.
firstHolderEnd
Indicates that the specified entity is the one who initially held something and that this holding relationship has come to an end.
-
D.
secondHolder
Indicates that an entity is the second person or party to hold or possess a particular item, role, title, or position in a sequence.
-
E.
termStartOfSecondHolder
Indicates that the term or tenure being referred to marks the beginning of the second holder’s period in that role or relationship.
- F. None of above. chosen
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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: May 3, 2026, 4:14 p.m.