Triple
T3190145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syriac Catholic Church |
E66801
|
entity |
| Predicate | preservesOwnCanonLaw |
P43362
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Syriac Catholic Church, preservesOwnCanonLaw, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservesOwnCanonLaw Context triple: [Syriac Catholic Church, preservesOwnCanonLaw, yes]
-
A.
preservesOwnLaw
Indicates that an entity maintains, upholds, or continues to follow its own established law or legal framework.
-
B.
hasOwnCanonLawParticularLaw
chosen
Indicates that an entity possesses its own specific set of canon or particular laws distinct from general or universal church law.
-
C.
usesCodeOfCanons
Indicates that one entity applies, follows, or is governed by a specified code of canons (a formal set of rules or laws).
-
D.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
-
E.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e67e948190afbd9cc6a3ade415 |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.