Triple
T10576077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angas |
E249614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | canonical text collection |
C10884
|
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: canonical text collection Context triple: [Angas, instanceOf, canonical text collection]
-
A.
canonical collection
chosen
A canonical collection is an organized set of items or elements arranged in a standard, authoritative form that uniquely represents all relevant variations or instances within a given context.
-
B.
critical edition of the Hebrew Bible
A critical edition of the Hebrew Bible is a scholarly reconstruction of the biblical text that compares and evaluates all major manuscripts and textual witnesses to present the most reliable form of the original writings, accompanied by an apparatus documenting significant variants.
-
C.
biblical text
A biblical text is a written work that forms part of the Bible, conveying religious narratives, laws, teachings, and poetry considered sacred and authoritative within Jewish and Christian traditions.
-
D.
majority text edition
A majority text edition is a critical version of a text that reconstructs its content by following the readings found in the majority of available manuscripts or textual witnesses.
-
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.
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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
Created at: April 6, 2026, 12:38 p.m.