Triple
T19868762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Mission on Monuments and Antiquities |
E477457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage documentation mission |
C42439
|
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: heritage documentation mission Context triple: [National Mission on Monuments and Antiquities, instanceOf, heritage documentation mission]
-
A.
heritage conservation document
A heritage conservation document is a formal record that outlines the historical significance, current condition, and recommended preservation strategies for a cultural heritage site, object, or landscape.
-
B.
cultural heritage database
A cultural heritage database is a structured digital repository that collects, organizes, and preserves information and media about historical artifacts, sites, traditions, and related cultural resources for research, education, and conservation.
-
C.
cultural heritage aggregator
A cultural heritage aggregator is a system that collects, harmonizes, and provides unified access to cultural artifacts, records, and metadata from multiple institutions and sources.
-
D.
heritage committee
A heritage committee is a group of appointed or elected individuals responsible for identifying, preserving, and advising on the protection and promotion of cultural, historical, or natural heritage resources within a community or organization.
-
E.
heritage centre
A heritage centre is a facility dedicated to preserving, interpreting, and presenting the historical, cultural, and natural heritage of a specific place or community for public education and engagement.
- F. None of above. chosen
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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:51 p.m.