Triple
T827126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglosphere |
E17878
|
entity |
| Predicate | hasSharedColonialHistory |
P20034
|
FINISHED |
| Object | British colonial rule |
—
|
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 colonial rule | Statement: [Anglosphere, hasSharedColonialHistory, British colonial rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSharedColonialHistory Context triple: [Anglosphere, hasSharedColonialHistory, British colonial rule]
-
A.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
B.
hasColonialName
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
C.
colonialLegacy
Indicates the enduring influence or consequences of a past colonial relationship that continue to shape interactions or conditions between entities.
-
D.
hadColonialAdministrationType
Indicates the specific form or system of colonial governance that was exercised over a territory or population.
-
E.
wasColonialPower
Indicates that one entity historically exercised colonial control or dominance over 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab989748819091a3809a747a1c5b |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4781c88190ae36906251347cdc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.