Triple
T37063220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Malaya |
E917375
|
entity |
| Predicate | secondHolderStart |
P125967
|
FINISHED |
| Object | 1960-04-14 |
—
|
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-04-14 | Statement: [King of Malaya, secondHolderStart, 1960-04-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondHolderStart Context triple: [King of Malaya, secondHolderStart, 1960-04-14]
-
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.
secondHolderServiceStart
chosen
Indicates that a second holder’s service or role has begun at a specific point in time.
-
C.
thirdHolderStart
Indicates the time or point at which a third holder (or third party in a sequence of holders) begins their involvement or possession in the relationship or process.
-
D.
secondCreationFirstHolder
Indicates that the first entity is the original holder or owner of the second entity at the time of its creation.
-
E.
secondCreationHolder
Indicates that an entity holds or possesses a secondary or subsequent creation associated with another entity or process.
- 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_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.