Triple
T14269246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dianmen Gate site |
E353734
|
entity |
| Predicate | hasPredecessor |
P97
|
FINISHED |
| Object | Dianmen Gate |
E1089349
|
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: Dianmen Gate | Statement: [Dianmen Gate site, hasPredecessor, Dianmen Gate]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dianmen Gate Context triple: [Dianmen Gate site, hasPredecessor, Dianmen Gate]
-
A.
Dianmen Gate
chosen
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.
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.
-
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.
Yonghe Gate
Yonghe Gate is the principal entrance to Beijing’s Yonghegong Lama Temple, a historic and architecturally significant Tibetan Buddhist monastery complex.
-
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 (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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de657fe6708190b41de48c43cff647 |
completed | April 14, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d16bae881909b38ccf04f1cf823 |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 10, 2026, 1:10 a.m.