Triple

T20305959
Position Surface form Disambiguated ID Type / Status
Subject Banwell E505608 entity
Predicate locatedNear P294 FINISHED
Object A371 road
The A371 road is a primary route in southwest England that connects several towns and villages in Somerset, serving as an important link between the A38 near Bristol Airport and the A37 near Shepton Mallet.
E1760649 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: A371 road | Statement: [Banwell, locatedNear, A371 road]
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: A371 road
Triple: [Banwell, locatedNear, A371 road]
Generated description
The A371 road is a primary route in southwest England that connects several towns and villages in Somerset, serving as an important link between the A38 near Bristol Airport and the A37 near Shepton Mallet.

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_69e0b4b8ab648190906e18538c250148 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6773f8f688190b616f972b9bbb28e completed April 20, 2026, 6:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12534b67048190b4c5d5021bbd26fa completed May 24, 2026, 1:24 a.m.
NEDg Description generation batch_6a1255b908b48190bd81bc6a3526ec09 completed May 24, 2026, 1:34 a.m.
NED2 Entity disambiguation (via description) batch_6a12562dd26c8190841d74d2c0d81ac8 completed May 24, 2026, 1:36 a.m.
Created at: April 16, 2026, 11:18 a.m.