Triple

T84350
Position Surface form Disambiguated ID Type / Status
Subject House of Deputies E1696 entity
Predicate organizationalLevel P275 FINISHED
Object churchwide 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: churchwide | Statement: [House of Deputies, organizationalLevel, churchwide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: organizationalLevel
Context triple: [House of Deputies, organizationalLevel, churchwide]
  • A. hasOrganizationalStructure
    Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
  • B. hasDivisionLevel chosen
    Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
  • C. levelOfGovernment
    Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
  • D. leftOrganization
    Indicates that an entity has departed from or is no longer affiliated with a particular organization.
  • E. meetsAtLevel
    Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
  • 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_69a24c8150408190910a693eb51c1f71 completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a24f4e73c081908d2da146226ef05e completed Feb. 28, 2026, 2:13 a.m.
PD Predicate disambiguation batch_69a24eb469548190b38c24e81f36c838 completed Feb. 28, 2026, 2:11 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.