Triple
T34273522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Orizaba |
E879388
|
entity |
| Predicate | isUnderCanonLaw |
P30517
|
FINISHED |
| Object | Code of Canon Law (1983) |
—
|
NE NERFINISHED |
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: Code of Canon Law (1983) | Statement: [Diocese of Orizaba, isUnderCanonLaw, Code of Canon Law (1983)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnderCanonLaw Context triple: [Diocese of Orizaba, isUnderCanonLaw, Code of Canon Law (1983)]
-
A.
hasPlaceInCanonLaw
Indicates that something holds a recognized status, role, or position within the system of canon law.
-
B.
usesCodeOfCanons
chosen
Indicates that one entity applies, follows, or is governed by a specified code of canons (a formal set of rules or laws).
-
C.
hasOwnCanonLawParticularLaw
Indicates that an entity possesses its own specific set of canon or particular laws distinct from general or universal church law.
-
D.
religiousCanonStatus
Indicates the status or standing of something with respect to its recognition or inclusion within a particular religious canon.
-
E.
canonLawJurisdiction
Indicates the scope or authority under which canon law applies to or governs a particular entity or matter.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:56 a.m.