Triple

T23339523
Position Surface form Disambiguated ID Type / Status
Subject Chang’an Gate E591696 entity
Predicate name P16 FINISHED
Object Chang’an Gate 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: Chang’an Gate | Statement: [Chang’an Gate, name, Chang’an Gate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chang’an Gate
Context triple: [Chang’an Gate, name, Chang’an Gate]
  • A. Chang’an Gate chosen
    Chang’an Gate is the prominent traditional-style entrance arch that serves as a symbolic gateway to Kobe’s Nankinmachi (Chinatown) district in Japan.
  • B. Xihua Gate
    Xihua Gate is a principal entrance to the Zhongnanhai leadership compound in Beijing, closely associated with the central government of the People’s Republic of China.
  • C. Shengji Gate
    Shengji Gate is a historic city gate in Qufu, China, associated with the city’s ancient walls and its rich Confucian heritage.
  • D. Daming Gate
    Daming Gate was a historic main gate of Beijing’s imperial city that served as a predecessor to the more famous Tiananmen Gate.
  • E. Zhonghua Gate
    Zhonghua Gate is a massive, well-preserved Ming dynasty fortress gate in Nanjing, China, renowned for its complex defensive design and historical significance.
  • 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_69e25d20156c81908c5c53195bd9c738 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f198317f4c8190a557cacb86568d6c completed April 29, 2026, 5:33 a.m.
Created at: April 17, 2026, 5:17 p.m.