Triple
T5671869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syllabus of Errors |
E124995
|
entity |
| Predicate | placeInCanonLaw |
P53692
|
FINISHED |
| Object | part of papal magisterium |
—
|
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: part of papal magisterium | Statement: [Syllabus of Errors, placeInCanonLaw, part of papal magisterium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInCanonLaw Context triple: [Syllabus of Errors, placeInCanonLaw, part of papal magisterium]
-
A.
hasPlaceInCanonLaw
chosen
Indicates that something holds a recognized status, role, or position within the system of canon law.
-
B.
hasPlaceInCanon
Indicates that something holds a specific status or position within an established canon or authoritative body of works.
-
C.
canonizedIn
Indicates that an authority formally declared someone to be a saint or holy figure in a specified place or institution.
-
D.
religiousCanonStatus
Indicates the status or standing of something with respect to its recognition or inclusion within a particular religious canon.
-
E.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.