Triple

T2515675
Position Surface form Disambiguated ID Type / Status
Subject Indian Malaysians E55406 entity
Predicate historicalMigrationReason P15033 FINISHED
Object plantation labour 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: plantation labour | Statement: [Indian Malaysians, historicalMigrationReason, plantation labour]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalMigrationReason
Context triple: [Indian Malaysians, historicalMigrationReason, plantation labour]
  • A. historicalMigrationType
    Indicates the type or category of migration that occurred in a historical context between entities.
  • B. historicalPopulationMovement
    Indicates the movement or migration of a population from one place to another during a specific historical period or event.
  • C. historicalReason chosen
    Indicates that one entity exists, occurs, or is justified because of causes, events, or circumstances rooted in the past of another entity.
  • D. immigratedTo
    Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
  • E. majorImmigrationPeriod
    Indicates that a time interval represents a significant period during which substantial immigration occurred.
  • 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_69ab49e4749c8190813311efd1630f1b completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd5a33234819082ad49fa6594b6be completed March 7, 2026, 7:37 a.m.
PD Predicate disambiguation batch_69abd0bf37c0819088d28b5081ba7556 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:46 p.m.