Triple

T1173957
Position Surface form Disambiguated ID Type / Status
Subject Great Kanto earthquake E24973 entity
Predicate homelessPeopleEstimate P1943 FINISHED
Object over 1.9 million 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: over 1.9 million | Statement: [Great Kanto earthquake, homelessPeopleEstimate, over 1.9 million]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: homelessPeopleEstimate
Context triple: [Great Kanto earthquake, homelessPeopleEstimate, over 1.9 million]
  • A. estimatedHomeless
    Indicates that a person or group is assessed or classified as likely experiencing homelessness, typically based on estimation rather than confirmed status.
  • 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. estimatedNumberEmancipated
    Indicates the estimated count of individuals who have been emancipated.
  • D. hasPopulationApproximate
    Indicates that an entity has an estimated or approximate population size, rather than an exact count.
  • E. populationIncludes
    Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
  • 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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd53e4b48190abb2167f8074a6bc completed March 1, 2026, 10:27 p.m.
PD Predicate disambiguation batch_69a4bb5844348190b01ac6506906ba3b completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:45 p.m.