Triple

T1422069
Position Surface form Disambiguated ID Type / Status
Subject Yugoslav Wars E30244 entity
Predicate refugeesAndIDPs P1943 FINISHED
Object millions 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: millions | Statement: [Yugoslav Wars, refugeesAndIDPs, millions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: refugeesAndIDPs
Context triple: [Yugoslav Wars, refugeesAndIDPs, millions]
  • A. civilianDisplacement
    Indicates the forced or compelled movement of civilian populations from their homes or usual places of residence, typically due to conflict, violence, or persecution.
  • B. displacedPeopleEstimate chosen
    Indicates an estimated number of people who have been forced to leave their homes or usual places of residence due to a particular event or situation.
  • C. hasRefugeePopulation
    Indicates that an entity hosts, contains, or is associated with a population of refugees.
  • D. humanitarianCrisis
    Indicates a situation in which a population faces severe, widespread threats to life, health, or basic living conditions that require urgent humanitarian assistance.
  • E. approximateNumberOfRefugeesTransported
    Indicates an estimated count of refugees who were transported in the described event or context.
  • 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_69a498fb823c8190a67ce4c4837e641a completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c52e4ed881908d85e0cb9fe851ac completed March 1, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69a4c4752abc8190a33b634c4d6fad28 completed March 1, 2026, 10:57 p.m.
Created at: March 1, 2026, 8 p.m.