Triple

T38391668
Position Surface form Disambiguated ID Type / Status
Subject Pentyrch E899735 entity
Predicate hasLocalGovernmentCommunityCouncil P38155 FINISHED
Object Pentyrch Community Council NE NERFINISHED

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: Pentyrch Community Council | Statement: [Pentyrch, hasLocalGovernmentCommunityCouncil, Pentyrch Community Council]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalGovernmentCommunityCouncil
Context triple: [Pentyrch, hasLocalGovernmentCommunityCouncil, Pentyrch Community Council]
  • A. hasLocalGovernmentCommunity
    Indicates that one entity possesses or is associated with a community-level local government authority responsible for administering that area.
  • B. hasCommunityCouncil chosen
    Indicates that an entity is governed, represented, or overseen by a community council.
  • C. hasLocalCouncilArea
    Indicates that an entity is located within, or is administratively governed by, a specific local council area.
  • D. districtCouncil
    Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
  • E. hasCountyCouncil
    Indicates that an entity is administratively governed or overseen by a specific county council.
  • 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_69f76e5c9b808190b486523f5c2f817d completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ffcb5536d88190bfc2e00b854cacfb completed May 10, 2026, 12:03 a.m.
PD Predicate disambiguation batch_69ffc900c2a081909dea04aa60566923 completed May 9, 2026, 11:53 p.m.
Created at: May 3, 2026, 4:31 p.m.