Triple
T26669164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceded Districts |
E672274
|
entity |
| Predicate | colonialTermUsedBy |
P17271
|
FINISHED |
| Object | British administrators |
—
|
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 administrators | Statement: [Ceded Districts, colonialTermUsedBy, British administrators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialTermUsedBy Context triple: [Ceded Districts, colonialTermUsedBy, British administrators]
-
A.
colonialNameUsedBy
chosen
Indicates that a colonial-era name for a place, group, or entity is used or applied by a particular agent or source.
-
B.
colonialTermMeaning
Indicates that a term or expression is used with a meaning rooted in or shaped by colonial contexts, perspectives, or power relations.
-
C.
usedInColonialPeriod
Indicates that something was utilized or in active use during a historical colonial period.
-
D.
preColonialUse
Indicates that something was used or occupied in a particular way during the period before colonial rule or colonization.
-
E.
usedInColonialAdministration
Indicates that something was employed as a tool, system, or resource within the structures or practices of colonial governance and administration.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 3:11 a.m.