Triple
T31393845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonine Order |
E800809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval religious order |
C60691
|
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 order Context triple: [Antonine Order, instanceOf, medieval religious order]
-
A.
religious-military order
A religious-military order is an organized group that combines a shared religious or spiritual mission with a structured, often hierarchical, military function or code of conduct.
-
B.
Catholic religious order
A Catholic religious order is a community of men or women in the Catholic Church who profess public vows and live a shared spiritual, communal, and often apostolic life according to a specific rule and charism.
-
C.
medieval religious movement
A medieval religious movement is a collective effort during the Middle Ages to reform, renew, or challenge existing religious beliefs and institutions, often blending spiritual, social, and political aims.
-
D.
medieval religious house
A medieval religious house is a community-based institution, such as a monastery, nunnery, or friary, where members of a religious order live under a rule, worship, and manage spiritual, educational, and economic activities.
-
E.
Benedictine congregation
A Benedictine congregation is an autonomous association of monasteries or religious communities that follow the Rule of St. Benedict and share common governance, spiritual traditions, and mission within the wider Benedictine Confederation.
- F. None of above. chosen
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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.