Triple
T9738453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gate of Heavenly Peace |
E236125
|
entity |
| Predicate | hasChineseName |
P4878
|
FINISHED |
| Object | 天安门 |
E234574
|
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: [Gate of Heavenly Peace, hasChineseName, 天安门]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 天安门 Context triple: [Gate of Heavenly Peace, hasChineseName, 天安门]
-
A.
天安门
chosen
天安门是位于北京市中心、作为中国象征性地标和重要政治历史事件发生地的著名城门与广场名称。
-
B.
午门
午门 is the grand southern entrance and main gate of Beijing’s Forbidden City, historically used for important imperial ceremonies and proclamations.
-
C.
太庙
太庙是北京故宫东侧一座明清皇家宗庙建筑群，现为对公众开放的历史文化景区。
-
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.
Bell Tower of Beijing
The Bell Tower of Beijing is a historic landmark in central Beijing that once housed a massive bell used to keep time for the city during imperial times.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef2ba048190811d6f4251fdb270 |
completed | April 1, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1c4083b208190b0e23c4dcbea0532 |
completed | April 5, 2026, 2:08 a.m. |
Created at: March 30, 2026, 8:22 p.m.