Triple
T17165070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon 70 |
E416586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval church document |
C11625
|
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: medieval church document Context triple: [Canon 70, instanceOf, medieval church document]
-
A.
medieval church
A medieval church is a religious building from the Middle Ages, typically characterized by stone construction, vaulted ceilings, stained glass windows, and architectural styles such as Romanesque or Gothic, serving as a center for worship and community life.
-
B.
ecclesiastical document
chosen
An ecclesiastical document is an official written instrument issued or authorized by a church authority that records, communicates, or regulates matters of faith, doctrine, worship, or church governance.
-
C.
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.
-
D.
medieval charter
A medieval charter is a formal written document, typically sealed by a ruler or authority, that records and grants legal rights, privileges, or property during the Middle Ages.
-
E.
church document
A church document is an official written record or statement produced by a religious institution to communicate doctrine, policy, liturgy, or administrative decisions.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.