Triple
T3848147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Heritage Sites in Delhi |
E85223
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of World Heritage Sites |
C11137
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: group of World Heritage Sites Context triple: [World Heritage Sites in Delhi, instanceOf, group of World Heritage Sites]
-
A.
group of historic sites
A group of historic sites is a collection of geographically or thematically related locations that hold recognized cultural, architectural, or historical significance and are often managed or interpreted as a unified whole.
-
B.
UNESCO World Heritage region
chosen
A UNESCO World Heritage region is a geographically defined area recognized by UNESCO for its outstanding universal value to humanity, encompassing natural, cultural, or mixed heritage that is legally protected and managed for long-term conservation.
-
C.
cultural site
A cultural site is a place of historical, artistic, social, or spiritual significance that embodies and preserves the traditions, values, and heritage of a community or civilization.
-
D.
national heritage site
A national heritage site is a location, structure, or landscape officially designated by a country as having significant historical, cultural, architectural, or natural value warranting legal protection and preservation.
-
E.
UNESCO biosphere reserve
A UNESCO biosphere reserve is a designated area that promotes solutions reconciling the conservation of biodiversity with its sustainable use, integrating protected ecosystems, research, and local community development.
- F. None of above.
Provenance (1 batch)
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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.