Triple

T1603576
Position Surface form Disambiguated ID Type / Status
Subject Han dynasty E34448 entity
Predicate currency P245 FINISHED
Object Ban Liang coin E181419 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: Ban Liang coin | Statement: [Han dynasty, currency, Ban Liang coin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ban Liang coin
Context triple: [Han dynasty, currency, Ban Liang coin]
  • A. Banliang coin chosen
    The Banliang coin was an early standardized round bronze coin with a square hole that became the model for later Chinese cash coins.
  • B. Xuan
    Xuan is a Vietnamese surname commonly used as a family name in Vietnam.
  • C. Jing
    Jing is a common Chinese surname shared by various notable figures across fields such as entertainment, sports, and academia.
  • D. piastre of French Indochina
    The piastre of French Indochina was the colonial monetary unit used across French-controlled territories in Southeast Asia, including present-day Vietnam, Laos, and Cambodia, during the late 19th and early 20th centuries.
  • E. Shi
    Shi is a Chinese surname historically associated with members of the Jewish community in Kaifeng, 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_69a885fea6a481909fe83ba6441f1774 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9094f96ec819090286c21b3dfddd5 completed March 5, 2026, 4:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad51bcdebc81909520786c560598b6 completed March 8, 2026, 10:38 a.m.
Created at: March 4, 2026, 7:28 p.m.