Triple

T2090696
Position Surface form Disambiguated ID Type / Status
Subject Orthodox Presbyterian Church E32661 entity
Predicate localGoverningBodies P9091 FINISHED
Object sessions 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: sessions | Statement: [Orthodox Presbyterian Church, localGoverningBodies, sessions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localGoverningBodies
Context triple: [Orthodox Presbyterian Church, localGoverningBodies, sessions]
  • A. governingBodyNearby
    Indicates that a governing body is located in close physical proximity to the referenced entity or area.
  • B. hasLocalGovernmentBody
    Indicates that an entity is administered or overseen by a specific local government authority or governing body.
  • C. governingBody2
    Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
  • D. municipalRepresentation
    Indicates that one entity serves as the official municipal-level representative or governing body for another entity within a specific locality or jurisdiction.
  • E. coordinationBody chosen
    Indicates that an entity serves as an organizing or governing body that coordinates the activities, policies, or interactions of other entities.
  • 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_69a885eba0708190999696a45cbec816 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abba7443448190a2642769d0b5fb93 completed March 7, 2026, 5:41 a.m.
PD Predicate disambiguation batch_69abb7b4356881909217c42ccb8bb1ed completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:43 p.m.