Triple

T25980819
Position Surface form Disambiguated ID Type / Status
Subject Bougainvillean communities in Australia E646063 entity
Predicate historicalMigrationContext P19590 FINISHED
Object Bougainville conflict 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: Bougainville conflict | Statement: [Bougainvillean communities in Australia, historicalMigrationContext, Bougainville conflict]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalMigrationContext
Context triple: [Bougainvillean communities in Australia, historicalMigrationContext, Bougainville conflict]
  • A. historicalMigrationType
    Indicates the type or category of migration that occurred in a historical context between entities.
  • B. historicalPopulationContext
    Indicates the relationship between a population figure and the specific historical period or circumstances in which that population size occurred.
  • C. historicalMigrationFactor
    Indicates that the relationship or condition is influenced by patterns, causes, or consequences of past human migration.
  • D. historicalPopulationMovement chosen
    Indicates the movement or migration of a population from one place to another during a specific historical period or event.
  • E. haveHistoricalMigrationWavesSince
    Indicates that there have been one or more significant migration waves involving the subject entity starting from a specified historical time onward.
  • 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_69e77e881fc08190ba1c8dc7e2a07f97 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f73ae120bc8190bff94d38d7a7a00d completed May 3, 2026, 12:09 p.m.
PD Predicate disambiguation batch_69f73a38d0848190aa5139144b8561c6 completed May 3, 2026, 12:06 p.m.
Created at: April 22, 2026, 8:54 a.m.