Triple
T33442880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NederlandstaligeKronieken |
E856412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical source collection |
C61740
|
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: historical source collection Context triple: [NederlandstaligeKronieken, instanceOf, historical source collection]
-
A.
historical source
A historical source is any original material—such as documents, artifacts, recordings, or testimonies—created in the past that provides evidence or information about historical events, people, or conditions.
-
B.
historical event collection
A historical event collection is an organized set of documented occurrences from the past, grouped and structured to support analysis, comparison, and retrieval based on time, place, theme, or significance.
-
C.
historical library
A historical library is an institution that collects, preserves, and provides access to books, manuscripts, and other records of the past to support research, education, and cultural memory.
-
D.
foundational document collection
A foundational document collection is an organized set of core, authoritative records that establish the essential principles, requirements, and context for a system, organization, or project.
-
E.
collection of ecclesiastical documents
A collection of ecclesiastical documents is an organized set of official church writings—such as decrees, letters, liturgical texts, and doctrinal statements—preserved for reference, governance, and historical record within a religious community.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.