Triple

T24949368
Position Surface form Disambiguated ID Type / Status
Subject South Asian Canadians E624283 entity
Predicate haveHistoricalMigrationWavesSince P157268 FINISHED
Object late 19th century 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: late 19th century | Statement: [South Asian Canadians, haveHistoricalMigrationWavesSince, late 19th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: haveHistoricalMigrationWavesSince
Context triple: [South Asian Canadians, haveHistoricalMigrationWavesSince, late 19th century]
  • A. historicalMigrationType
    Indicates the type or category of migration that occurred in a historical context between entities.
  • B. historicalMigrationFactor
    Indicates that the relationship or condition is influenced by patterns, causes, or consequences of past human migration.
  • C. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • D. hasMigrationHistoryFrom
    Indicates that an entity has a recorded history of migrating or moving from a specified origin location or source.
  • E. hasHistoricalOriginInYear
    Indicates that something first originated, began, or came into existence in a specified calendar year.
  • 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_69e2ff22e4c48190a0444b5a044f14e8 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f423fea68881908d5a9984ad5e944b completed May 1, 2026, 3:54 a.m.
PD Predicate disambiguation batch_69f4210130d08190ae30b7943f7a0bbc completed May 1, 2026, 3:41 a.m.
PDg Predicate description generation batch_69f423637bec8190a1701421ac86a3b7 completed May 1, 2026, 3:52 a.m.
Created at: April 18, 2026, 5:55 a.m.