Triple
T4060398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 颐和园 |
E86196
|
entity |
| Predicate | 世界遗产标准 |
P18553
|
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.
UNESCOWorldHeritageCriteria
Indicates that a site meets one or more of the official UNESCO World Heritage criteria used to justify its inscription on the World Heritage List.
-
B.
UNESCOWorldHeritageReason
chosen
Indicates the justification or criteria for which something has been designated as a UNESCO World Heritage site.
-
C.
UNESCOSiteType
Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
-
D.
UNESCOHeritage
Indicates that a place, site, or cultural/natural asset has been officially inscribed on the UNESCO World Heritage List as having outstanding universal value.
-
E.
hasWorldHeritageSite
Indicates that a location or entity possesses or contains a site designated as a UNESCO World Heritage Site.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.