Triple
T28808067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLFP |
E727433
|
entity |
| Predicate | hasPrimeMinisterOfSriLanka |
P9370
|
FINISHED |
| Object | Sirimavo Bandaranaike |
—
|
NE NERFINISHED |
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: Sirimavo Bandaranaike | Statement: [SLFP, hasPrimeMinisterOfSriLanka, Sirimavo Bandaranaike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimeMinisterOfSriLanka Context triple: [SLFP, hasPrimeMinisterOfSriLanka, Sirimavo Bandaranaike]
-
A.
hasPresidentOfSriLanka
Indicates that one entity serves as the president of Sri Lanka in relation to another entity.
-
B.
coPrimeMinisterWith
Indicates that two individuals simultaneously hold the position of prime minister together, sharing the role as co–prime ministers.
-
C.
hasChiefMinisterFrom
Indicates that a political or administrative region has a chief minister whose origin, affiliation, or source is from a specified entity.
-
D.
appointedAsGovernorOfCeylon
Indicates that an entity was formally appointed to serve in the official role of Governor of Ceylon.
-
E.
primeMinisterFrom
chosen
Indicates that a person serves or has served as the prime minister of a specified country, region, or political entity.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 28, 2026, 6:29 a.m.