Triple
T30180637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | territory of Ceylon |
E767189
|
entity |
| Predicate | wasCrownColonyOf |
P3075
|
FINISHED |
| Object | United 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: United Kingdom | Statement: [territory of Ceylon, wasCrownColonyOf, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCrownColonyOf Context triple: [territory of Ceylon, wasCrownColonyOf, United Kingdom]
-
A.
partOfColonialEntity
Indicates that one entity is a constituent or subordinate territorial unit within a larger colonial political or administrative entity.
-
B.
wasColonialPower
chosen
Indicates that one entity historically exercised colonial control or dominance over another entity.
-
C.
formerColonialStatus
Indicates that one entity previously held colonial authority or control over another entity, but that colonial relationship has since ended.
-
D.
formerColonyName
Indicates that one entity is the historical or previous name used for a colony that later changed its political status or designation.
-
E.
broughtUnderBritishCrown
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f419e088190ba19a6ab9465d951 |
completed | May 2, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:26 p.m.