Triple
T3278644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhengyangmen |
E68818
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 正阳门 |
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: 正阳门 | Statement: [Zhengyangmen, nativeName, 正阳门]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 正阳门 Context triple: [Zhengyangmen, nativeName, 正阳门]
-
A.
午门
午门 is the grand southern entrance and main gate of Beijing’s Forbidden City, historically used for important imperial ceremonies and proclamations.
-
B.
天安门
天安门是位于北京市中心、作为中国象征性地标和重要政治历史事件发生地的著名城门与广场名称。
-
C.
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.
-
D.
Drum Tower of Beijing
The Drum Tower of Beijing is a historic landmark in central Beijing that once served as the city’s official timekeeping center, featuring a large drum hall and panoramic views of the surrounding old city.
-
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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0155430819097c806ee407dc1e4 |
completed | March 8, 2026, 5:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2e84ddd24819094a47269023f9889 |
completed | March 12, 2026, 4:22 p.m. |
Created at: March 8, 2026, 3:10 p.m.