Triple

T21211132
Position Surface form Disambiguated ID Type / Status
Subject Consul Solon Han E522721 entity
Predicate familyName P18 FINISHED
Object Han NE NERFINISHED

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 | Statement: [Consul Solon Han, familyName, Han]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Han
Context triple: [Consul Solon Han, familyName, Han]
  • A. Han chosen
    Han refers to the majority ethnic group in China, historically associated with Chinese civilization, language, and culture.
  • B. Han
    Han is a common transliteration of the historical Central Asian title "Khan," often associated with rulers and nobility in various Turkic and Mongolic cultures.
  • C. Hal
    Hal is a masculine given name, commonly used as a diminutive form of Harold.
  • D. Hannen
    Hannen is an English surname associated with several notable figures, including actors and judges, in British history.
  • E. Hane
    Hane is a small coastal village on the Marquesan island of Ua Huka in French Polynesia, known for its archaeological sites and traditional Polynesian culture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5112d8881909510b2dcdc93106d completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7346eb20c8190aeb3c0cc0a24aaf9 completed April 21, 2026, 8:25 a.m.
Created at: April 16, 2026, 3:37 p.m.