Triple
T25524127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinhalese kingdoms of Sri Lanka |
E639732
|
entity |
| Predicate | successorKingdom |
P168537
|
FINISHED |
| Object | Polonnaruwa Kingdom |
—
|
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: Polonnaruwa Kingdom | Statement: [Sinhalese kingdoms of Sri Lanka, successorKingdom, Polonnaruwa Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorKingdom Context triple: [Sinhalese kingdoms of Sri Lanka, successorKingdom, Polonnaruwa Kingdom]
-
A.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
B.
successorSovereign
Indicates that one entity becomes the next ruling sovereign following another entity, inheriting their position of supreme authority.
-
C.
successorRuler
Indicates that one ruler directly follows another in holding a position of authority or rule.
-
D.
successorInNorthernLands
Indicates that one entity becomes the next holder of a role, title, or position specifically within the context of the Northern Lands.
-
E.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 21, 2026, 3:09 p.m.