Triple

T151318
Position Surface form Disambiguated ID Type / Status
Subject Province of Canterbury E3436 entity
Predicate followsPolity P1815 FINISHED
Object episcopal polity 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: episcopal polity | Statement: [Province of Canterbury, followsPolity, episcopal polity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: followsPolity
Context triple: [Province of Canterbury, followsPolity, episcopal polity]
  • A. hasPolity chosen
    Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
  • B. politicalFunction
    Indicates that an entity holds, performs, or is associated with a specific role, duty, or function within a political system or structure.
  • C. politicalPattern
    Indicates a recurring or characteristic way in which political behaviors, decisions, or power dynamics are organized or expressed.
  • D. relatedLegislation
    Indicates that there exists a legislative document that is connected to, affects, or is otherwise relevant to the subject entity.
  • E. politicalRationale
    Indicates the reasoning, justification, or strategic considerations underlying a political decision, stance, or action.
  • 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_69a252868de4819080e21c9938bfe8b6 completed Feb. 28, 2026, 2:27 a.m.
NER Named-entity recognition batch_69a2580f55a88190b37b54ee0ed5ac7c completed Feb. 28, 2026, 2:50 a.m.
PD Predicate disambiguation batch_69a2565adaf48190b68ae4444ff83ccd completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:31 a.m.