Triple

T12658461
Position Surface form Disambiguated ID Type / Status
Subject Hezhen language E302350 entity
Predicate alternativeName P39 FINISHED
Object Hezhe E491944 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: Hezhe | Statement: [Hezhen language, alternativeName, Hezhe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hezhe
Context triple: [Hezhen language, alternativeName, Hezhe]
  • A. Hezhe chosen
    The Hezhe are a small Tungusic ethnic group in northeastern China, traditionally known for fishing and hunting along the Amur and Ussuri rivers and for their distinctive riverine culture.
  • B. Hechi
    Hechi is a prefecture-level city in northwestern Guangxi, China, known for its karst landscapes, ethnic diversity, and rich mineral resources.
  • C. Teisheba
    Teisheba is the Urartian storm and war god, often associated with thunder, rain, and military power in the ancient Near Eastern pantheon.
  • D. Sanhe
    Sanhe is a county-level city in northern China’s Hebei province, administered by the prefecture-level city of Langfang near the Beijing–Tianjin region.
  • E. Hua
    Hua is a Chinese given name commonly used for both males and females, often associated with meanings like "flower" or "China."
  • 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_69d7bded71a88190bb76e2413af9ea66 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d961636db8819099c438b24bcfd866 completed April 10, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c730b5c8190ae8dbb476e53729e completed May 2, 2026, 10:36 p.m.
Created at: April 9, 2026, 5:19 p.m.