Triple

T33716598
Position Surface form Disambiguated ID Type / Status
Subject Skeldergate Bridge E863890 entity
Predicate connects P390 FINISHED
Object Bishopgate Street
Bishopgate Street is a road in the historic city of York, England, situated near the River Ouse and linked to the city’s central areas via Skeldergate Bridge.
E2119139 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: Bishopgate Street | Statement: [Skeldergate Bridge, connects, Bishopgate Street]
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: Bishopgate Street
Triple: [Skeldergate Bridge, connects, Bishopgate Street]
Generated description
Bishopgate Street is a road in the historic city of York, England, situated near the River Ouse and linked to the city’s central areas via Skeldergate Bridge.

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_69f34989871c81908682e22a2fe4b829 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fae5adbc8190ad5c1576ab1b0687 completed May 3, 2026, 7:36 a.m.
NED1 Entity disambiguation (via context triple) batch_6a37a892cb588190ae9e8741278f75af completed June 21, 2026, 9:02 a.m.
NEDg Description generation batch_6a37a9a50f1c819085a8f3c03b11a415 completed June 21, 2026, 9:06 a.m.
NED2 Entity disambiguation (via description) batch_6a37ab6826d48190a95fcf8f2b40186a completed June 21, 2026, 9:14 a.m.
Created at: May 1, 2026, 1:44 a.m.