Triple

T17433715
Position Surface form Disambiguated ID Type / Status
Subject Gilling East E423943 entity
Predicate hasParishChurchCharacteristic P121209 FINISHED
Object historic architecture 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: historic architecture | Statement: [Gilling East, hasParishChurchCharacteristic, historic architecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasParishChurchCharacteristic
Context triple: [Gilling East, hasParishChurchCharacteristic, historic architecture]
  • A. parishChurchFeatures
    Indicates that a parish church possesses or includes specific architectural, artistic, or functional features.
  • B. hasVillageChurchCharacter
    Indicates that something possesses the qualities or characteristics typically associated with a village church.
  • C. 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.
  • D. hasParishChurchArchitecturalInterest chosen
    Indicates that a parish church possesses notable architectural features or significance.
  • E. hasParishChurchesIn
    Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or 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_69d889d88b6081908bada047f5b3ba51 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4490274608190a60ada9aeb246eff completed April 19, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69e3b030eac481909b8402719cc3102e completed April 18, 2026, 4:24 p.m.
Created at: April 10, 2026, 5:46 a.m.