Triple
T10499146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andingmen Station |
E247620
|
entity |
| Predicate | servesArea |
P82
|
FINISHED |
| Object | Andingmen |
E247620
|
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: Andingmen | Statement: [Andingmen Station, servesArea, Andingmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Andingmen Context triple: [Andingmen Station, servesArea, Andingmen]
-
A.
Andingmen
chosen
Andingmen is a historic area and former city gate site in central Beijing, known for its traditional neighborhoods and proximity to key cultural landmarks.
-
B.
Taiping Gate
Taiping Gate is one of the historic city gates incorporated into the ancient defensive walls of Nanjing, China.
-
C.
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.
-
D.
Shengji Gate
Shengji Gate is a historic city gate in Qufu, China, associated with the city’s ancient walls and its rich Confucian heritage.
-
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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098e45ec8190a02b981a06786909 |
completed | April 7, 2026, 1:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d8dcc5816c8190a6a3927797942266 |
completed | April 10, 2026, 11:19 a.m. |
Created at: April 6, 2026, 12:25 p.m.