Triple

T30770698
Position Surface form Disambiguated ID Type / Status
Subject Pegu region E783514 entity
Predicate wasColonialAdministrativeAreaWithin P95255 FINISHED
Object British Burma 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: British Burma | Statement: [Pegu region, wasColonialAdministrativeAreaWithin, British Burma]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasColonialAdministrativeAreaWithin
Context triple: [Pegu region, wasColonialAdministrativeAreaWithin, British Burma]
  • A. partOfColonialEntity chosen
    Indicates that one entity is a constituent or subordinate territorial unit within a larger colonial political or administrative entity.
  • B. wasColonialPower
    Indicates that one entity historically exercised colonial control or dominance over another entity.
  • C. hadColonialAdministrationType
    Indicates the specific form or system of colonial governance that was exercised over a territory or population.
  • D. hasColonialAdministrativeCategory
    Indicates that an entity is classified under a specific category within a colonial administrative system or hierarchy.
  • E. underColonialAdministrativeUnit
    Indicates that one entity functioned within the jurisdiction or authority of a specified colonial administrative unit.
  • 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_69f224b1519081908b9db003fd2073e0 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f68fc1913081909b621a90cb555115 completed May 2, 2026, 11:58 p.m.
PD Predicate disambiguation batch_69f686140aa08190a35f62572b2db9b6 completed May 2, 2026, 11:17 p.m.
Created at: April 29, 2026, 8:40 p.m.