Triple
T15251195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand the Holy Prince |
E364521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman Catholic layperson |
C29395
|
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: Roman Catholic layperson Context triple: [Ferdinand the Holy Prince, instanceOf, Roman Catholic layperson]
-
A.
Christian layperson
chosen
A Christian layperson is a non-ordained member of the Christian community who practices and lives out their faith in everyday life without holding formal clerical office.
-
B.
Catholic lay leader
A Catholic lay leader is a non-ordained member of the Church who assumes responsibility for guiding, organizing, and serving the faith community in collaboration with clergy and according to Catholic teaching.
-
C.
Roman Catholic cleric
A Roman Catholic cleric is an ordained minister in the Roman Catholic Church, such as a deacon, priest, or bishop, who performs sacred rites, administers sacraments, and provides spiritual leadership to the faithful.
-
D.
English Catholic priest
An English Catholic priest is an ordained minister of the Roman Catholic Church in England who leads worship, administers sacraments, provides pastoral care, and represents the Catholic faith within English society.
-
E.
19th-century Roman Catholic priest
A 19th-century Roman Catholic priest is a clergyman ordained within the Catholic Church during the 1800s, responsible for administering sacraments, preaching, pastoral care, and often engaging with the social, political, and intellectual currents of the era.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.