Triple
T2718785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule for Anchoresses |
E60030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval religious text |
C1507
|
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 religious text Context triple: [Rule for Anchoresses, instanceOf, medieval religious text]
-
A.
medieval prose text
chosen
A medieval prose text is a written work from the Middle Ages composed in continuous, non-verse form, often preserving narratives, religious teachings, legal codes, or historical accounts in the vernacular or Latin.
-
B.
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.
-
C.
religious text carrier
A religious text carrier is an entity (person, object, or medium) that transports, preserves, or conveys sacred writings from one place, time, or audience to another.
-
D.
religious literature
Religious literature is a body of written works—such as scriptures, theological treatises, devotional texts, and spiritual narratives—created to express, interpret, and transmit the beliefs, practices, values, and experiences of a religious tradition.
-
E.
religious scripture
A religious scripture is a revered written text or collection of texts that a faith community regards as divinely inspired or authoritative in matters of belief, morality, and spiritual practice.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:55 p.m.