Triple
T8938519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instrumentum Laboris for the 2014 Extraordinary Synod on the Family |
E212837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | synod preparatory 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: synod preparatory document Context triple: [Instrumentum Laboris for the 2014 Extraordinary Synod on the Family, instanceOf, synod preparatory document]
-
A.
synodal final report
A synodal final report is an official document summarizing the discussions, discernments, decisions, and recommendations that emerge from a synod’s deliberative process.
-
B.
post-synodal apostolic exhortation
A post-synodal apostolic exhortation is a formal papal document issued after a meeting of the Synod of Bishops that summarizes its discussions, offers guidance, and sets pastoral priorities for the Church on the topic addressed.
-
C.
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.
-
D.
pastoral constitution
A pastoral constitution is an official teaching document of the Catholic Church, issued by an ecumenical council, that addresses doctrinal principles in relation to the practical, pastoral needs and life of the contemporary world.
-
E.
theological document
A theological document is a written work that systematically explores, explains, or argues about religious beliefs, doctrines, and practices within a particular faith tradition.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:58 p.m.