Triple
T27176269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Responsorial Psalm |
E683050
|
entity |
| Predicate | textApprovedBy |
P807
|
FINISHED |
| Object | ecclesiastical authority |
—
|
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: ecclesiastical authority | Statement: [Responsorial Psalm, textApprovedBy, ecclesiastical authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textApprovedBy Context triple: [Responsorial Psalm, textApprovedBy, ecclesiastical authority]
-
A.
approvedBy
chosen
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
B.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
C.
isApprovedFor
Indicates that one entity has been officially authorized, accepted, or permitted for use, access, or association with another entity.
-
D.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
E.
publicApproval
Indicates the degree to which the general public supports, agrees with, or has a favorable opinion of a person, action, policy, or entity.
- F. None of above.
Provenance (3 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6257a5ae881908db3032511378836 |
completed | May 2, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:26 a.m.