Triple

T30065863
Position Surface form Disambiguated ID Type / Status
Subject Arlesey E764029 entity
Predicate governingBody P46 FINISHED
Object Arlesey Town Council
Arlesey Town Council is the local parish-level governing authority responsible for representing and managing community affairs in the town of Arlesey, Bedfordshire, England.
E1896300 NE 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: Arlesey Town Council | Statement: [Arlesey, governingBody, Arlesey Town Council]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Arlesey Town Council
Triple: [Arlesey, governingBody, Arlesey Town Council]
Generated description
Arlesey Town Council is the local parish-level governing authority responsible for representing and managing community affairs in the town of Arlesey, Bedfordshire, England.

Provenance (5 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_69f2247221388190a13a22c47094a0ef completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67ca660c081909ef3662275121a4e completed May 2, 2026, 10:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2732502ae481908ae28a9a72ecf130 completed June 8, 2026, 9:21 p.m.
NEDg Description generation batch_6a273467a5a08190a12fcef30d6e6b67 completed June 8, 2026, 9:30 p.m.
NED2 Entity disambiguation (via description) batch_6a2734d963048190bdd26f2b580a3b41 completed June 8, 2026, 9:32 p.m.
Created at: April 29, 2026, 6:59 p.m.