Triple

T32622365
Position Surface form Disambiguated ID Type / Status
Subject Trescowe E833961 entity
Predicate hasCivilParishType P13874 FINISHED
Object rural 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: rural | Statement: [Trescowe, hasCivilParishType, rural]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCivilParishType
Context triple: [Trescowe, hasCivilParishType, rural]
  • A. hasCivilParishComponent
    Indicates that an entity includes or is composed of the specified civil parish as one of its administrative components.
  • B. hasCivilParishStatus
    Indicates that an entity holds the official administrative status or designation of a civil parish.
  • C. hasParishType chosen
    Indicates that an entity is associated with or classified by a specific type or category of parish.
  • D. onlyCivilParishOf
    Indicates that one entity is the sole civil parish associated with, or contained within, the other entity, with no other civil parishes sharing that association.
  • E. hasCivilParishName
    Indicates that an entity has a specific civil parish name as its designated official name at the civil parish 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_69f3492ccc80819086ef7d26e9786647 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f78fd5a6388190bfda4bbb2e222e5b completed May 3, 2026, 6:11 p.m.
PD Predicate disambiguation batch_69f78e2ac3fc819081a45c6841375c8d completed May 3, 2026, 6:04 p.m.
Created at: May 1, 2026, 1:06 a.m.