Triple

T17071711
Position Surface form Disambiguated ID Type / Status
Subject Jiaqing Emperor E414236 entity
Predicate deathPlace P21 FINISHED
Object Rehe E380255 NE 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: Rehe | Statement: [Jiaqing Emperor, deathPlace, Rehe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rehe
Context triple: [Jiaqing Emperor, deathPlace, Rehe]
  • A. Rehe chosen
    Rehe was a historical province in northeastern China that served as a strategic frontier region between the Great Wall and Manchuria.
  • B. Reh
    Reh is a major traditional festival of the Idu Mishmi tribe in Arunachal Pradesh, celebrated with elaborate rituals, dances, and communal feasting to honor deities and seek prosperity.
  • C. Reopalu
    Reopalu is a small settlement located in Järva County in central Estonia.
  • D. ReEn
    ReEn is a Korean beauty and personal care brand from LG Household & Health Care known for its haircare and skincare products that often incorporate traditional herbal ingredients.
  • E. Rhees
    Rhees is a surname of Welsh origin borne by various notable individuals in fields such as philosophy, education, and public service.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d886cef44c8190ba56c44b4e863e64 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbc1b7d48190979a848b4188cb22 completed April 18, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012edbce988190a784448ba8a258a5 completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:34 a.m.