Triple
T37063221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Malaya |
E917375
|
entity |
| Predicate | secondHolderEnd |
P163911
|
FINISHED |
| Object | 1960-09-01 |
—
|
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-01 | Statement: [King of Malaya, secondHolderEnd, 1960-09-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondHolderEnd Context triple: [King of Malaya, secondHolderEnd, 1960-09-01]
-
A.
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.
-
B.
thirdHolderEnd
Indicates that an entity serves as the third holder or recipient at the end point of a holding or transfer relationship.
-
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.
termEndOfSecondHolder
chosen
Indicates that something marks or corresponds to the ending point of a second holder’s term or tenure in a role or relationship.
-
E.
secondHolderHouse
Indicates that an entity is the second person or party to hold or occupy a particular house or dwelling.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:14 p.m.