Triple
T28652823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W. Dahanayake |
E725245
|
entity |
| Predicate | termStartAsPrimeMinisterOfCeylon |
P370
|
FINISHED |
| Object | 1959-09-26 |
—
|
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: 1959-09-26 | Statement: [W. Dahanayake, termStartAsPrimeMinisterOfCeylon, 1959-09-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsPrimeMinisterOfCeylon Context triple: [W. Dahanayake, termStartAsPrimeMinisterOfCeylon, 1959-09-26]
-
A.
primeMinisterTermStart
chosen
Indicates the date on which an individual officially begins serving as prime minister.
-
B.
endTimeFirstTermAsPrimeMinister
Indicates the date and time when an individual’s first term serving as prime minister comes to an end.
-
C.
firstPrimeMinisterTermStart
Indicates the date on which an entity began serving its first term as prime minister.
-
D.
termStartAsActingPrimeMinister
Indicates that a person’s term in office begins specifically in the capacity of acting prime minister, rather than as a fully appointed or elected prime minister.
-
E.
primeMinisterAtStart
Indicates that the subject was serving as prime minister at the beginning of a specified period or event.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:53 a.m.