Triple

T14823568
Position Surface form Disambiguated ID Type / Status
Subject Qianmen Street E348514 entity
Predicate near P350 FINISHED
Object Qianmen Gate E68818 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: Qianmen Gate | Statement: [Qianmen Street, near, Qianmen Gate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Qianmen Gate
Context triple: [Qianmen Street, near, Qianmen Gate]
  • A. Dianmen Gate
    Dianmen Gate was a historic northern gate of Beijing’s Imperial City, once forming part of the traditional north–south central axis before its demolition.
  • B. Zhengyangmen (Qianmen Gate) chosen
    Zhengyangmen (Qianmen Gate) is a historic and iconic southern gate of Beijing’s old city wall, serving as a prominent landmark and symbol of the capital’s imperial past.
  • C. Yonghe Gate
    Yonghe Gate is the principal entrance to Beijing’s Yonghegong Lama Temple, a historic and architecturally significant Tibetan Buddhist monastery complex.
  • D. Andingmen Gate
    Andingmen Gate was a historic northern gate of Beijing’s old city wall, once serving as a key entrance and defensive structure before its demolition in the 20th century.
  • E. Yongdingmen
    Yongdingmen is a historic southern gate site of Beijing’s old city wall, now a reconstructed landmark and traffic node at the southern end of the city’s central axis.
  • 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_69d822eb8f588190bf53445e730a934f completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decfe7a8dc8190bcb5ecfa1cbf1601 completed April 14, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe389d7c848190813be06bed7813d7 completed May 8, 2026, 7:25 p.m.
Created at: April 10, 2026, 1:51 a.m.