Triple

T33021687
Position Surface form Disambiguated ID Type / Status
Subject Bedminster Down E844927 entity
Predicate hasRoad P959 FINISHED
Object Parson Street
Parson Street is a road in the Bedminster Down area of Bristol, England, known for serving local residential neighborhoods and connecting them to the wider city road network.
E2291768 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: Parson Street | Statement: [Bedminster Down, hasRoad, Parson 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: Parson Street
Triple: [Bedminster Down, hasRoad, Parson Street]
Generated description
Parson Street is a road in the Bedminster Down area of Bristol, England, known for serving local residential neighborhoods and connecting them to the wider city road network.

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_69f34950749c8190ae05cd27adb16d58 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d2b0a69c81909631ae3a866d1a95 completed May 3, 2026, 4:44 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5c8a9bf704819083e84fdd742cbaad completed July 19, 2026, 8:28 a.m.
NEDg Description generation batch_6a5c8ae8c9fc819085fed61c7b1c0a80 completed July 19, 2026, 8:29 a.m.
NED2 Entity disambiguation (via description) batch_6a5c8b5b90d8819091ce6081508200ad completed July 19, 2026, 8:31 a.m.
Created at: May 1, 2026, 1:23 a.m.