Triple

T13363534
Position Surface form Disambiguated ID Type / Status
Subject Cheung E318877 entity
Predicate hasVariant P455 FINISHED
Object Cheong E321784 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: Cheong | Statement: [Cheung, hasVariant, Cheong]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cheong
Context triple: [Cheung, hasVariant, Cheong]
  • A. Cheong chosen
    Cheong is a variant transliteration of the Chinese surname commonly romanized as Zhang, used in certain dialects and regional naming conventions.
  • B. Cheonji
    Cheonji is the high-altitude crater lake atop Paektu Mountain on the border of China and North Korea, renowned for its scenic beauty and volcanic origin.
  • C. Koung-Khi
    Koung-Khi is an administrative department located in the West Region of Cameroon.
  • D. Yeoncheon
    Yeoncheon is a county in Gyeonggi Province, South Korea, known for its location near the Demilitarized Zone (DMZ) and its significant historical and military sites.
  • E. Myeong-bok
    Myeong-bok is the given name of Gojong, the 26th king of the Joseon dynasty and first emperor of the Korean Empire.
  • 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_69d806b7bbac8190b85278c87fa7aff3 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69da628affd081909f1790d333f0eef4 completed April 11, 2026, 3:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7267c99788190b158b1d9f57ceba2 completed May 3, 2026, 10:42 a.m.
Created at: April 9, 2026, 9:32 p.m.