Triple
T9307559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman synod of 610 |
E223924
|
entity |
| Predicate | governedByCanonLaw |
P75418
|
FINISHED |
| Object | early medieval canon law |
—
|
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: early medieval canon law | Statement: [Roman synod of 610, governedByCanonLaw, early medieval canon law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByCanonLaw Context triple: [Roman synod of 610, governedByCanonLaw, early medieval canon law]
-
A.
canonLawContext
chosen
Indicates that something occurs within, is governed by, or is interpreted according to the norms and framework of canon law.
-
B.
canonLawSubject
Indicates that an entity is the subject or topic governed, regulated, or addressed by a particular canon law or set of canonical legal norms.
-
C.
canonLawAction
Indicates an action, decision, or procedure carried out under or in accordance with canon law.
-
D.
usesCodeOfCanons
Indicates that one entity applies, follows, or is governed by a specified code of canons (a formal set of rules or laws).
-
E.
hasOwnCanonLawParticularLaw
Indicates that an entity possesses its own specific set of canon or particular laws distinct from general or universal church law.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daa21188190b1b2e508b0d09dcb |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.