Triple
T2278827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theology of the Body |
E51233
|
entity |
| Predicate | formOfWork |
P36545
|
FINISHED |
| Object | Wednesday general audience catecheses |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Wednesday general audience catecheses | Statement: [Theology of the Body, formOfWork, Wednesday general audience catecheses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formOfWork Context triple: [Theology of the Body, formOfWork, Wednesday general audience catecheses]
-
A.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
B.
formTreatment
Indicates that one entity creates, establishes, or defines a particular treatment or therapeutic regimen for another entity.
-
C.
employsForm
Indicates that an entity makes use of or applies a particular form or format in carrying out an action or function.
-
D.
constructionForm
Indicates the method, style, or structural technique by which something is built or constructed.
-
E.
filingForm
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
- F. None of above. chosen
Provenance (4 batches)
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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc217b6648190be77d2176d322efd |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:48 p.m.