Triple

T13666212
Position Surface form Disambiguated ID Type / Status
Subject Jin (state) E327125 entity
Predicate notableClans P111063 FINISHED
Object Han clan E705269 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: Han clan | Statement: [Jin (state), notableClans, Han clan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Han clan
Context triple: [Jin (state), notableClans, Han clan]
  • A. Han clan chosen
    The Han clan was one of the powerful aristocratic lineages in ancient China that emerged as a major feudal state following the breakup of the Jin kingdom during the Warring States period.
  • B. Ji clan
    The Ji clan was the aristocratic lineage that held hereditary power as the ruling family of the ancient Chinese State of Yan during the Zhou dynasty period.
  • C. Ji clan
    The Ji clan was one of the three powerful aristocratic lineages that dominated the politics of the ancient Chinese State of Lu during the Spring and Autumn period.
  • D. Enghee clan
    The Enghee clan is a distinct social or familial group associated with the community or lineage of Teron.
  • E. Sun clan
    The Sun clan was the ruling family of the Eastern Wu state during China’s Three Kingdoms period, producing warlords such as Sun Quan who established and led the regime.
  • 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_69d8076d8270819092afc2f0e9c359a8 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc8746458819095ec1ba3c01ef31b completed April 12, 2026, 4:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7943bfaf0819097410e901847d77c completed May 3, 2026, 6:30 p.m.
Created at: April 9, 2026, 9:52 p.m.