Triple

T26332411
Position Surface form Disambiguated ID Type / Status
Subject Süd E662422 entity
Predicate hasTransportConnection P845 FINISHED
Object Ludwigshafen bus network
The Ludwigshafen bus network is the local public bus system serving the city of Ludwigshafen am Rhein and its surrounding districts in southwestern Germany.
E1720034 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: Ludwigshafen bus network | Statement: [Süd, hasTransportConnection, Ludwigshafen bus network]
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: Ludwigshafen bus network
Triple: [Süd, hasTransportConnection, Ludwigshafen bus network]
Generated description
The Ludwigshafen bus network is the local public bus system serving the city of Ludwigshafen am Rhein and its surrounding districts in southwestern Germany.

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_69ee812f32748190871d970c4e2a8ddf completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60f69fd248190bb747dde86643732 completed May 2, 2026, 2:51 p.m.
NED1 Entity disambiguation (via context triple) batch_6a119a59f8048190a6aa7c10fb9f851d completed May 23, 2026, 12:15 p.m.
NEDg Description generation batch_6a119ad502f4819094bacc5b50514200 completed May 23, 2026, 12:17 p.m.
NED2 Entity disambiguation (via description) batch_6a119b5af6f48190a607628edf5bd0c8 completed May 23, 2026, 12:19 p.m.
Created at: April 26, 2026, 10:34 p.m.