Triple

T31594346
Position Surface form Disambiguated ID Type / Status
Subject Nomocanon of Ibn al-ʿAssal E806181 entity
Predicate inCanonLawTraditionOf P138523 FINISHED
Object Coptic Orthodox Church 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: Coptic Orthodox Church | Statement: [Nomocanon of Ibn al-ʿAssal, inCanonLawTraditionOf, Coptic Orthodox Church]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inCanonLawTraditionOf
Context triple: [Nomocanon of Ibn al-ʿAssal, inCanonLawTraditionOf, Coptic Orthodox Church]
  • A. 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.
  • B. canonLawTraining
    Indicates that one entity has provided or received training or education in canon law in relation to another entity.
  • C. canonLawContext
    Indicates that something occurs within, is governed by, or is interpreted according to the norms and framework of canon law.
  • D. canonLawContribution
    Indicates a contribution an entity makes to the development, interpretation, or application of canon law.
  • E. canonLawJurisdiction chosen
    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_69f348d4891c8190b02bae3c8ecb68b7 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a8332a008190949520bac1f9a0b0 completed May 3, 2026, 1:43 a.m.
PD Predicate disambiguation batch_69f6a75656e081908739ed9e2f600e42 completed May 3, 2026, 1:39 a.m.
Created at: April 30, 2026, 10:29 p.m.