Triple

T31034733
Position Surface form Disambiguated ID Type / Status
Subject Ormskirk E790823 entity
Predicate hasParishChurchFeature P38425 FINISHED
Object combined tower and spire 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: combined tower and spire | Statement: [Ormskirk, hasParishChurchFeature, combined tower and spire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasParishChurchFeature
Context triple: [Ormskirk, hasParishChurchFeature, combined tower and spire]
  • A. hasParishChurchesIn
    Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
  • B. parishChurchFeatures chosen
    Indicates that a parish church possesses or includes specific architectural, artistic, or functional features.
  • C. hasCathedralParish
    Indicates that a cathedral is associated with or served by a specific parish within an ecclesiastical jurisdiction.
  • D. isActiveParishChurch
    Indicates that a church currently functions as the main parish church for a community and is actively in use for parish activities and services.
  • E. isParishChurch
    Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
  • 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_69f224c97a788190b5da1ead6038a74e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe7b1c506c8190869c1a22031e0571 completed May 9, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69fe796b2bdc8190a86980d44008f875 completed May 9, 2026, 12:01 a.m.
Created at: April 29, 2026, 8:59 p.m.