Triple

T23369470
Position Surface form Disambiguated ID Type / Status
Subject Aldwark E593421 entity
Predicate hasNotableStructure P105 FINISHED
Object Aldwark Bridge
Aldwark Bridge is a historic toll bridge over the River Ure in North Yorkshire, England, serving as a key local crossing between the villages of Aldwark and Great Ouseburn.
E1611896 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: Aldwark Bridge | Statement: [Aldwark, hasNotableStructure, Aldwark 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: Aldwark Bridge
Triple: [Aldwark, hasNotableStructure, Aldwark Bridge]
Generated description
Aldwark Bridge is a historic toll bridge over the River Ure in North Yorkshire, England, serving as a key local crossing between the villages of Aldwark and Great Ouseburn.

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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0aff84c8190a5a6bf52adae1c9a completed April 29, 2026, 6:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f7e4076508190ad05af30fb3cc8ea completed May 21, 2026, 9:50 p.m.
NEDg Description generation batch_6a0f7effdaec8190ad809bb1f17fa883 completed May 21, 2026, 9:54 p.m.
NED2 Entity disambiguation (via description) batch_6a0f7f84f8c881909f889b0b0ef7fd27 completed May 21, 2026, 9:56 p.m.
Created at: April 17, 2026, 5:32 p.m.