Triple

T36378261
Position Surface form Disambiguated ID Type / Status
Subject River Blyth E895968 entity
Predicate hasBridge P386 FINISHED
Object Blyth Old Bridge
Blyth Old Bridge is a historic stone road bridge in Northumberland, England, notable for carrying traffic across the River Blyth near the town of Blyth.
 E2282847 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: Blyth Old Bridge | Statement: [River Blyth, hasBridge, Blyth Old Bridge]
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: Blyth Old Bridge
Triple: [River Blyth, hasBridge, Blyth Old Bridge]
Generated description
Blyth Old Bridge is a historic stone road bridge in Northumberland, England, notable for carrying traffic across the River Blyth near the town of Blyth.

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_69f76e51d358819092bbc5f119f49476 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bb191af8819085752b8046efc840 completed May 3, 2026, 9:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a422ba1286c8190a2bba713774686ba completed June 29, 2026, 8:24 a.m.
NEDg Description generation batch_6a422c27fcd48190b18dc28056a71a96 completed June 29, 2026, 8:26 a.m.
NED2 Entity disambiguation (via description) batch_6a422c7bb5008190ad708c4f89958071 completed June 29, 2026, 8:27 a.m.
Created at: May 3, 2026, 4:10 p.m.