Triple

T31463047
Position Surface form Disambiguated ID Type / Status
Subject Yaghnobi people E802654 entity
Predicate returnMigration P4275 FINISHED
Object partial return to Yaghnob Valley 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: partial return to Yaghnob Valley | Statement: [Yaghnobi people, returnMigration, partial return to Yaghnob Valley]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: returnMigration
Context triple: [Yaghnobi people, returnMigration, partial return to Yaghnob Valley]
  • A. migrationFrom
    Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
  • B. migration chosen
    Indicates the movement of entities from one location or context to another, often across boundaries or over time.
  • C. supportsMigrationOf
    Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
  • D. returnMission
    Indicates that an entity goes back to its original location or base after completing a mission or task.
  • E. migrationProgram
    Indicates that there is a structured plan or scheme designed to manage, support, or regulate the movement or relocation of entities from one place or system to another.
  • 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_69f348c84c1c81908739f100ecf7394e completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f75dc25fa08190b371faf36d9fb72c completed May 3, 2026, 2:37 p.m.
PD Predicate disambiguation batch_69f758586534819083e91172f4bf5098 completed May 3, 2026, 2:14 p.m.
Created at: April 30, 2026, 9:21 p.m.