Triple

T5036403
Position Surface form Disambiguated ID Type / Status
Subject Gojoseon E113433 entity
Predicate neighbor P350 FINISHED
Object Yan (state) E195965 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: Yan (state) | Statement: [Gojoseon, neighbor, Yan (state)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yan (state)
Context triple: [Gojoseon, neighbor, Yan (state)]
  • A. state of Yan chosen
    The state of Yan was an ancient Chinese kingdom located in the northeastern region of China, which played a significant role as one of the major powers during the Warring States period.
  • B. Yan
    Yan is a Chinese surname historically borne by various notable figures and families across different regions of China.
  • C. Yanyou
    Yanyou was a reign era of the Yuan dynasty under Emperor Ayurbarwada Buyantu Khan in the early 14th century.
  • D. Yanam
    Yanam is a coastal town and district enclave of the Union Territory of Puducherry in India, historically influenced by French colonial rule and culturally linked to the Telugu-speaking region of Andhra Pradesh.
  • E. Deyu
    Deyu is the courtesy name of the Hongguang Emperor, a short-lived Southern Ming ruler who attempted to restore the Ming dynasty after the fall of Beijing to the Qing.
  • 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_69bd44384298819089c49e7c330ec7b8 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73bb069c8190af86f1b2f95f3d95 completed March 20, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69be9c79265081908512b39cc74161f8 completed March 21, 2026, 1:26 p.m.
Created at: March 20, 2026, 1:37 p.m.