Triple

T26772594
Position Surface form Disambiguated ID Type / Status
Subject Mbojo people E670018 entity
Predicate hasDemographicConcentration P70368 FINISHED
Object Bima Regency 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: Bima Regency | Statement: [Mbojo people, hasDemographicConcentration, Bima Regency]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDemographicConcentration
Context triple: [Mbojo people, hasDemographicConcentration, Bima Regency]
  • A. hasPopulationConcentrationIn chosen
    Indicates that a population is densely or significantly clustered within a specified geographic area or region.
  • B. hasDemographicCenter
    Indicates that an entity has a primary geographic location where the majority or core concentration of its associated population or demographic group is found.
  • C. hasDemographicPresenceIn
    Indicates that a particular demographic group exists or is represented within a specified geographic area or population context.
  • D. hasDemographic
    Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
  • E. populationConcentration
    Indicates the degree to which a population is densely gathered or distributed within a specific area or region.
  • 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_69eeb31c925881909b597f6e40056d28 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 27, 2026, 4:03 a.m.