Triple
T12388601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacra Tridentina Synodus |
E295932
|
entity |
| Predicate | approvedInForma |
P43142
|
FINISHED |
| Object | in forma specifica by Pope Pius X |
—
|
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: in forma specifica by Pope Pius X | Statement: [Sacra Tridentina Synodus, approvedInForma, in forma specifica by Pope Pius X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedInForma Context triple: [Sacra Tridentina Synodus, approvedInForma, in forma specifica by Pope Pius X]
-
A.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
B.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
C.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
D.
approvedInCountry
Indicates that an entity has received official authorization or approval within the jurisdiction of a specified country.
-
E.
approvalMethod
chosen
Indicates the method or process by which approval is granted or obtained between entities.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fcf6aa8819080c9a2407a72db2e |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.