Triple

T32335546
Position Surface form Disambiguated ID Type / Status
Subject ZBA E826160 entity
Predicate servedByLine P1293 FINISHED
Object DLR (Docklands Light Railway)
DLR (Docklands Light Railway) is an automated light metro system serving the redeveloped Docklands area and surrounding districts in East and Southeast London.
E2002135 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: DLR (Docklands Light Railway) | Statement: [ZBA, servedByLine, DLR (Docklands Light Railway)]
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: DLR (Docklands Light Railway)
Triple: [ZBA, servedByLine, DLR (Docklands Light Railway)]
Generated description
DLR (Docklands Light Railway) is an automated light metro system serving the redeveloped Docklands area and surrounding districts in East and Southeast London.

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_69f34913d9048190befaa634025232be completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6be189f848190b9826b97b1191f26 completed May 3, 2026, 3:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3057283bd0819091b28cd0ed1ac837 completed June 15, 2026, 7:48 p.m.
NEDg Description generation batch_6a305fd3fb4c81909addd45e71304664 completed June 15, 2026, 8:25 p.m.
NED2 Entity disambiguation (via description) batch_6a30606681748190b69350f9ca12d264 completed June 15, 2026, 8:28 p.m.
Created at: May 1, 2026, 12:48 a.m.