Triple

T23133251
Position Surface form Disambiguated ID Type / Status
Subject Stoneferry Bridge E577235 entity
Predicate hasApproachRoad P4067 FINISHED
Object Stoneferry Road
Stoneferry Road is a main thoroughfare in Kingston upon Hull, England, serving as a key route for traffic approaching and crossing the River Hull via Stoneferry Bridge.
E2285324 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: Stoneferry Road | Statement: [Stoneferry Bridge, hasApproachRoad, Stoneferry 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: Stoneferry Road
Triple: [Stoneferry Bridge, hasApproachRoad, Stoneferry Road]
Generated description
Stoneferry Road is a main thoroughfare in Kingston upon Hull, England, serving as a key route for traffic approaching and crossing the River Hull via Stoneferry 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_69e245f7b0e481909c473ff4e6a54e2c completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e89cce881908727a94dbc00e031 completed April 29, 2026, 4:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a45de0026148190bed57ae1a6231ce6 completed July 2, 2026, 3:41 a.m.
NEDg Description generation batch_6a45e17550708190a47e578d2a95f142 completed July 2, 2026, 3:56 a.m.
NED2 Entity disambiguation (via description) batch_6a45e20cc2ac8190b9d40c2e6e17fc76 completed July 2, 2026, 3:59 a.m.
Created at: April 17, 2026, 4 p.m.