Triple
T9692814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天安门 |
E234574
|
entity |
| Predicate | 在中国形象中的作用 |
P3795
|
FINISHED |
| Object | 常用于代表中国的标志性图像 |
—
|
LITERAL 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: [天安门, 在中国形象中的作用, 常用于代表中国的标志性图像]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 在中国形象中的作用 Context triple: [天安门, 在中国形象中的作用, 常用于代表中国的标志性图像]
-
A.
ChineseObjective
Indicates that an entity has an objective, goal, or target specifically related to China or the Chinese context.
-
B.
hasCulturalRole
chosen
Indicates that an entity fulfills or is assigned a specific function, position, or significance within a cultural, social, or traditional context.
-
C.
roleInBeltAndRoad
Indicates the specific function, involvement, or capacity an entity has within the context of the Belt and Road Initiative.
-
D.
iconographicFunction
Indicates the symbolic or representational role that something serves within an image or visual composition.
-
E.
roleInTaiwan
Indicates that an entity holds or has held an official or notable role, position, or function within the political, administrative, or social context of Taiwan.
- F. None of above.
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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0727908190897894151c0ee7c2 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.