Triple
T14841337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chongwenmen station |
E348970
|
entity |
| Predicate | hasNativeName |
P1435
|
FINISHED |
| Object | 崇文门站 |
E909312
|
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: [Chongwenmen station, hasNativeName, 崇文门站]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 崇文门站 Context triple: [Chongwenmen station, hasNativeName, 崇文门站]
-
A.
崇文门
chosen
崇文门是北京明清时期内城东南部的一座重要城门遗址及地名，如今也是地铁与商业区的交通枢纽。
-
B.
阜成门
阜成门是北京旧城西部的一座历史城门遗址，曾是明清时期京城重要的出入口之一。
-
C.
安定门
安定门是北京旧城北部的一座历史城门遗址及地名，现为重要交通枢纽和地标区域。
-
D.
Qianmen Station of Beijing Subway
Qianmen Station of the Beijing Subway is a central metro station near Tiananmen Square that serves as a key access point to Beijing’s historic Qianmen and Zhengyangmen areas.
-
E.
午门
午门 is the grand southern entrance and main gate of Beijing’s Forbidden City, historically used for important imperial ceremonies and proclamations.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded28fa49c81908d1059e6cafd607f |
completed | April 14, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe38a9eb9481908ca509f484007cf6 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:53 a.m.