Triple

T38510141
Position Surface form Disambiguated ID Type / Status
Subject Practice and Procedure in the Church of Scotland E921879 entity
Predicate requiresUpdating P63095 FINISHED
Object true 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: true | Statement: [Practice and Procedure in the Church of Scotland, requiresUpdating, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresUpdating
Context triple: [Practice and Procedure in the Church of Scotland, requiresUpdating, true]
  • A. requiresUpdate chosen
    Indicates that an entity must be refreshed, modified, or brought to a newer state before it can be considered current or valid.
  • B. requiresChangeTo
    Indicates that one entity can only be fulfilled, valid, or completed if another entity is modified or altered first.
  • C. requiresUpgrade
    Indicates that one entity cannot function as intended or reach a desired state unless it is updated or enhanced to a newer or higher version.
  • D. requiresRestart
    Indicates that performing this action or applying this change necessitates restarting the relevant system, service, or application for it to take effect.
  • E. renewalRequired
    Indicates that an existing agreement, status, or authorization must be renewed to remain valid.
  • 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_69f76ea3c5448190aa7002fc1ba3f874 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a00b6199c348190b1e90375f737d026 completed May 10, 2026, 4:45 p.m.
PD Predicate disambiguation batch_6a00b5169a7881909a07167c4188731f completed May 10, 2026, 4:40 p.m.
Created at: May 3, 2026, 4:32 p.m.