Triple
T16733685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linnaean correspondence |
E406661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical correspondence collection |
C7716
|
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 correspondence collection Context triple: [Linnaean correspondence, instanceOf, historical correspondence collection]
-
A.
letter collection
chosen
A letter collection is an organized set of written or printed correspondence, often preserved for personal, historical, or literary significance.
-
B.
personal papers collection
A personal papers collection is an organized body of documents and materials created, received, and accumulated by an individual that reflects their life, work, and activities.
-
C.
diplomatic archive
A diplomatic archive is an organized collection of official records, correspondence, treaties, and related documents produced or received by a state's diplomatic services, preserved for legal, historical, and administrative purposes.
-
D.
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.
-
E.
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.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.