Triple

T21261444
Position Surface form Disambiguated ID Type / Status
Subject M32 motorway E524011 entity
Predicate hasJunctionWith P1018 FINISHED
Object A432 road
The A432 road is a regional route in South Gloucestershire and Bristol, England, connecting local towns and suburbs and linking them to major roads including the M32 motorway.
E2291575 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: A432 road | Statement: [M32 motorway, hasJunctionWith, A432 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: A432 road
Triple: [M32 motorway, hasJunctionWith, A432 road]
Generated description
The A432 road is a regional route in South Gloucestershire and Bristol, England, connecting local towns and suburbs and linking them to major roads including the M32 motorway.

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_69e0b5156d7881909bd4f83676590715 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e735e6a0448190ad412a8fcbbd8ff0 completed April 21, 2026, 8:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5c700f6ab0819093a4dceb9e836f37 completed July 19, 2026, 6:34 a.m.
NEDg Description generation batch_6a5c7065aa7c8190aa81b69dfb61a199 completed July 19, 2026, 6:36 a.m.
NED2 Entity disambiguation (via description) batch_6a5c70b55cac8190a31b49f6b1bff735 completed July 19, 2026, 6:37 a.m.
Created at: April 16, 2026, 3:59 p.m.