Triple
T16718911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco-Roman sources |
E406293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical source corpus |
C6136
|
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 corpus Context triple: [Greco-Roman sources, instanceOf, historical source corpus]
-
A.
historical source
chosen
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.
bibliographical corpus
A bibliographical corpus is a structured collection of bibliographic records or references, typically compiled for systematic analysis, cataloging, or research on published works.
-
C.
reference corpus
A reference corpus is a large, structured collection of texts compiled to represent a particular language, genre, or domain, used as an authoritative basis for linguistic analysis, comparison, and research.
-
D.
historical linguistic document
A historical linguistic document is a written or recorded artifact from the past that provides evidence about the language, its usage, and its evolution in a particular historical context.
-
E.
documentation corpus
A documentation corpus is a structured collection of written materials, such as manuals, guides, and reference texts, compiled to provide comprehensive information and support for a specific domain, product, or system.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.