Triple

T3005461
Position Surface form Disambiguated ID Type / Status
Subject Innocentius PP. IV E81888 entity
Predicate legalExpertise P25968 FINISHED
Object 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: canon law | Statement: [Innocentius PP. IV, legalExpertise, canon law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalExpertise
Context triple: [Innocentius PP. IV, legalExpertise, canon law]
  • A. legalBackground chosen
    Indicates that an entity has education, training, or experience related to law or the legal profession.
  • B. legalRepresentation
    Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
  • C. legalContext
    Indicates that the relationship or action occurs within, is shaped by, or is relevant to a specific legal framework, proceeding, or set of legal norms.
  • D. legalDoctrine
    Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
  • E. legalCase
    Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a15ad9c81908255003bdb38d603 completed March 8, 2026, 3:47 p.m.
PD Predicate disambiguation batch_69ad96180eb08190a524c5f458d41382 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3 p.m.