Triple
T19868713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Mission for Manuscripts |
E477456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | manuscript conservation programme |
C2057
|
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: manuscript conservation programme Context triple: [National Mission for Manuscripts, instanceOf, manuscript conservation programme]
-
A.
heritage conservation programme
chosen
A heritage conservation programme is an organized set of policies, actions, and resources aimed at identifying, protecting, and sustainably managing cultural and natural heritage for present and future generations.
-
B.
manuscript catalogue
A manuscript catalogue is a systematically organized listing that describes and indexes individual manuscripts within a collection, typically including details such as authorship, date, provenance, physical characteristics, and content summaries.
-
C.
manuscript museum
A manuscript museum is an institution dedicated to collecting, preserving, studying, and exhibiting historical and culturally significant handwritten documents and texts.
-
D.
manuscript collection
A manuscript collection is an organized group of handwritten, typed, or otherwise unpublished documents, often related by creator, subject, or provenance, preserved and managed as a single archival unit.
-
E.
ancient manuscripts
Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:51 p.m.