Triple
T21711599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | monks of Gloucester Abbey |
E535919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Christian religious community |
C22086
|
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 Christian religious community Context triple: [monks of Gloucester Abbey, instanceOf, medieval Christian religious community]
-
A.
medieval religious house
chosen
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.
-
B.
Catholic religious house
A Catholic religious house is a residence where members of a Catholic religious community live, pray, and carry out their spiritual and communal activities under a shared rule of life.
-
C.
group of Christian monks
A group of Christian monks is a community of men who live together under religious vows, dedicating their lives to prayer, contemplation, and communal service according to a shared monastic rule.
-
D.
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.
-
E.
Anglican religious community
An Anglican religious community is a group of men or women within the Anglican tradition who live under a common rule of life, sharing prayer, worship, and service in a vowed or committed communal setting.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:46 p.m.