Triple
T3216781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jingshan Park |
E67415
|
entity |
| Predicate | hasChineseName |
P4878
|
FINISHED |
| Object | 景山公园 |
E67415
|
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: [Jingshan Park, hasChineseName, 景山公园]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 景山公园 Context triple: [Jingshan Park, hasChineseName, 景山公园]
-
A.
颐和园
颐和园是位于北京市西北部、以宏伟的皇家园林建筑和昆明湖、万寿山自然景观著称的世界文化遗产。
-
B.
天安门
天安门是位于北京市中心、作为中国象征性地标和重要政治历史事件发生地的著名城门与广场名称。
-
C.
Jingshan Park
chosen
Jingshan Park is a historic imperial garden and scenic hilltop park in central Beijing, offering panoramic views over the Forbidden City and the surrounding cityscape.
-
D.
蛇山
蛇山 is a well-known hill in Wuhan, Hubei Province, China, noted for its scenic views over the Yangtze River and its historical and cultural significance.
-
E.
Beijing Garden Expo Park
Beijing Garden Expo Park is a large ecological and cultural park in Beijing known for its extensive themed gardens, landscape architecture, and venues for horticultural exhibitions and leisure activities.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab096b588190b22e41a76263ae92 |
completed | March 8, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b26241803c8190aa3254d5887c80f4 |
completed | March 12, 2026, 6:50 a.m. |
Created at: March 8, 2026, 3:08 p.m.