Triple
T3253326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’an Avenue |
E68236
|
entity |
| Predicate | passesBy |
P3947
|
FINISHED |
| Object | Fuxingmen |
E73684
|
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: Fuxingmen | Statement: [Chang’an Avenue, passesBy, Fuxingmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fuxingmen Context triple: [Chang’an Avenue, passesBy, Fuxingmen]
-
A.
Chongwenmen
Chongwenmen is a historic gate area in central Beijing that once formed part of the old city wall and now serves as a major commercial and transportation hub.
-
B.
Fuchengmen
Fuchengmen is a historic gate area in Beijing that once formed part of the old city wall and now serves as a major traffic and commercial hub.
-
C.
Fuxingmen station
chosen
Fuxingmen station is a major interchange stop on the Beijing Subway, serving as a key transfer point between multiple central city lines.
-
D.
Fuchengmen station
Fuchengmen station is an underground metro station in Beijing serving the central Xicheng District as part of the city’s extensive subway network.
-
E.
Chongwenmen station
Chongwenmen station is a major interchange stop on the Beijing Subway serving central Beijing near the historic Chongwenmen gate area.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf640fd8819083c3c0cc41db2ffc |
completed | March 8, 2026, 5:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b36093ae9081909f6e63b1efcb9fbb |
completed | March 13, 2026, 12:55 a.m. |
Created at: March 8, 2026, 3:09 p.m.