Triple

T19066059
Position Surface form Disambiguated ID Type / Status
Subject Ketagalan Boulevard E466661 entity
Predicate near P350 FINISHED
Object Control Yuan 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: Control Yuan | Statement: [Ketagalan Boulevard, near, Control Yuan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Control Yuan
Context triple: [Ketagalan Boulevard, near, Control Yuan]
  • A. Control Yuan chosen
    The Control Yuan is one of the five branches of government in the Republic of China (Taiwan), responsible for oversight, auditing, and impeachment of public officials.
  • B. Zongzhang
    Zongzhang was a brief Chinese imperial era name used during the reign of Emperor Gaozong of the Tang dynasty.
  • C. Yuanzhong
    Yuanzhong was the courtesy name of Cao Rui, the second emperor of the state of Cao Wei during China’s Three Kingdoms period.
  • D. Consort Yuan
    Consort Yuan was an imperial consort of the late Ming dynasty and wife of the Chongzhen Emperor, associated with the dynasty’s final years before its collapse.
  • E. Zhidong
    Zhidong is the given name of Zhang Zhidong, a prominent late Qing dynasty Chinese official and reformer.
  • 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_69d8dd04f4488190b1121cc53ef2bfd6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e198621481908618f65dd01746fc completed April 20, 2026, 8:19 a.m.
Created at: April 10, 2026, 12:03 p.m.