Triple
T3019728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nayakkar dynasty |
E82424
|
entity |
| Predicate | endedWithEvent |
P3587
|
FINISHED |
| Object | British annexation of Kandy in 1815 |
—
|
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: British annexation of Kandy in 1815 | Statement: [Nayakkar dynasty, endedWithEvent, British annexation of Kandy in 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedWithEvent Context triple: [Nayakkar dynasty, endedWithEvent, British annexation of Kandy in 1815]
-
A.
endedWith
chosen
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
B.
concludedAtEvent
Indicates that an entity’s participation, state, or validity ended as a result of a specific event.
-
C.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
D.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
E.
endedFor
Indicates that a particular event, state, or process has come to an end for a specified entity or participant.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a940c048190bc46e2c8001db8c0 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.