Triple

T2364927
Position Surface form Disambiguated ID Type / Status
Subject Anglican Use E47358 entity
Predicate preservesElement P17760 FINISHED
Object Anglican liturgical heritage 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: Anglican liturgical heritage | Statement: [Anglican Use, preservesElement, Anglican liturgical heritage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: preservesElement
Context triple: [Anglican Use, preservesElement, Anglican liturgical heritage]
  • A. preservesFeature chosen
    Indicates that one entity maintains or keeps intact a particular feature, property, or characteristic of another entity during some process or interaction.
  • B. preservesAsTimeOf
    Indicates that one entity maintains or records another entity specifically as a temporal reference or time-related designation.
  • C. preservedExample
    Indicates that an example instance has been kept intact or maintained in its original state for future reference or use.
  • D. usesElement
    Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
  • E. preservesOwnLaw
    Indicates that an entity maintains, upholds, or continues to follow its own established law or legal framework.
  • 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_69a88a1a4a6081908645b0f2914521ab completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abc7486cb48190acef1891cc87bdb1 completed March 7, 2026, 6:35 a.m.
PD Predicate disambiguation batch_69abc599b92c819093d9e15d4437705d completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:55 p.m.