Triple

T36414679
Position Surface form Disambiguated ID Type / Status
Subject Three Mills E896972 entity
Predicate hasNearbyInfrastructure P231 FINISHED
Object Three Mills Lock
Three Mills Lock is a modern tidal lock on the Prescott Channel in East London, built to improve navigation and water management around the historic Three Mills area.
 E2185898 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: Three Mills Lock | Statement: [Three Mills, hasNearbyInfrastructure, Three Mills Lock]
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: Three Mills Lock
Triple: [Three Mills, hasNearbyInfrastructure, Three Mills Lock]
Generated description
Three Mills Lock is a modern tidal lock on the Prescott Channel in East London, built to improve navigation and water management around the historic Three Mills area.

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_69f76e54ce408190849acc3f7758937c completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bd3275b88190a84791b747f3f3f6 completed May 3, 2026, 9:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39cfc1120c8190ab7c2b397f96e0a7 completed June 23, 2026, 12:13 a.m.
NEDg Description generation batch_6a39d2a54e888190b2d5677a01152eec completed June 23, 2026, 12:26 a.m.
NED2 Entity disambiguation (via description) batch_6a39d3fdead881908075c5228cf851d6 completed June 23, 2026, 12:31 a.m.
Created at: May 3, 2026, 4:10 p.m.