Triple
T16233515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 圜丘坛 |
E394046
|
entity |
| Predicate | 所属世界遗产 |
P4220
|
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.
hasWorldHeritageSite
Indicates that a location or entity possesses or contains a site designated as a UNESCO World Heritage Site.
-
B.
UNESCOWorldHeritageSiteComponentOf
chosen
Indicates that one entity is a component or constituent part of a larger UNESCO World Heritage Site.
-
C.
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.
-
D.
UNESCOWorldHeritageSiteWithin
Indicates that a UNESCO World Heritage Site is geographically located within the boundaries of a specified area or region.
-
E.
UNESCOWorldHeritageSiteRelated
Indicates a relationship where one entity is designated as, part of, or otherwise officially associated with 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2be2f881908ec2483507cb0b00 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.