Triple

T32573592
Position Surface form Disambiguated ID Type / Status
Subject Caldon Canal E832580 entity
Predicate hasLock P2431 FINISHED
Object Froghall Locks
Froghall Locks is a flight of canal locks near Froghall in Staffordshire, England, known for marking the terminus of the Caldon Canal and providing access toward the Churnet Valley.
E2011737 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: Froghall Locks | Statement: [Caldon Canal, hasLock, Froghall Locks]
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: Froghall Locks
Triple: [Caldon Canal, hasLock, Froghall Locks]
Generated description
Froghall Locks is a flight of canal locks near Froghall in Staffordshire, England, known for marking the terminus of the Caldon Canal and providing access toward the Churnet Valley.

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_69f34927bb308190ad94da1b11cad13c completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c63ca2e881909f8e056c1ed181ba completed May 3, 2026, 3:51 a.m.
NED1 Entity disambiguation (via context triple) batch_6a347b9d8c488190906f11ded59938e9 completed June 18, 2026, 11:13 p.m.
NEDg Description generation batch_6a347c9f8bc48190b83503d479a75958 completed June 18, 2026, 11:17 p.m.
NED2 Entity disambiguation (via description) batch_6a347d6a097881909f078a5dbbdf4e1f completed June 18, 2026, 11:21 p.m.
Created at: May 1, 2026, 1:04 a.m.