Triple
T36036968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kandyan law |
E1042429
|
entity |
| Predicate | statusAfterColonialPeriod |
P200563
|
FINISHED |
| Object | partially retained |
—
|
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: partially retained | Statement: [Kandyan law, statusAfterColonialPeriod, partially retained]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterColonialPeriod Context triple: [Kandyan law, statusAfterColonialPeriod, partially retained]
-
A.
colonialEraStatus
Indicates the status or condition an entity held specifically during a colonial historical period.
-
B.
colonialLegacy
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
C.
periodOfColonialRule
Indicates the time span during which one political power exercised colonial control over another territory or people.
-
D.
preColonialStatus
Indicates the condition, role, or social-political standing an entity held prior to the onset of colonial rule.
-
E.
colonialChange
Indicates a change in colonial status or control of a territory, such as gaining, losing, or altering colonial rule.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69ff965eef90819097499d1f0542378c |
completed | May 9, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:07 p.m.