Triple

T31581407
Position Surface form Disambiguated ID Type / Status
Subject A4232 Peripheral Distributor Road E805832 entity
Predicate hasJunctionWith P1018 FINISHED
Object A4055 at Cardiff Bay
A4055 at Cardiff Bay is a section of the A4055 road serving the Cardiff Bay area and connecting it to the wider Cardiff road network.
E1969331 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: A4055 at Cardiff Bay | Statement: [A4232 Peripheral Distributor Road, hasJunctionWith, A4055 at Cardiff Bay]
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: A4055 at Cardiff Bay
Triple: [A4232 Peripheral Distributor Road, hasJunctionWith, A4055 at Cardiff Bay]
Generated description
A4055 at Cardiff Bay is a section of the A4055 road serving the Cardiff Bay area and connecting it to the wider Cardiff 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_69f348d3a86c8190a3e5e539a4dd125f completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a80977a88190bd64c02801a72e0b completed May 3, 2026, 1:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b564c30f08190ad3751888ca7da18 completed June 12, 2026, 12:43 a.m.
NEDg Description generation batch_6a2b5a24195c8190a040aea5c19ad47c completed June 12, 2026, 1 a.m.
NED2 Entity disambiguation (via description) batch_6a2b6d32b9608190a15eac23c418ff9c completed June 12, 2026, 2:21 a.m.
Created at: April 30, 2026, 10:23 p.m.