Triple

T29530399
Position Surface form Disambiguated ID Type / Status
Subject Ardingly E749185 entity
Predicate hasParishCouncil P3379 FINISHED
Object Ardingly Parish Council
Ardingly Parish Council is the local governing body responsible for representing and managing community affairs in the village of Ardingly, West Sussex, England.
E1871249 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: Ardingly Parish Council | Statement: [Ardingly, hasParishCouncil, Ardingly Parish 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: Ardingly Parish Council
Triple: [Ardingly, hasParishCouncil, Ardingly Parish Council]
Generated description
Ardingly Parish Council is the local governing body responsible for representing and managing community affairs in the village of Ardingly, West Sussex, 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_69f0bd46d99c81908ba9d01cc1dbef7d completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66ca093c88190bf7be3679440e5a6 completed May 2, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a260c34ba7c81909d062839cbfd627f completed June 8, 2026, 12:26 a.m.
NEDg Description generation batch_6a26103bff1c8190a5852e827db5715c completed June 8, 2026, 12:43 a.m.
NED2 Entity disambiguation (via description) batch_6a26143093dc819089620614744485cd completed June 8, 2026, 1 a.m.
Created at: April 28, 2026, 4:52 p.m.