Triple

T29061891
Position Surface form Disambiguated ID Type / Status
Subject Leipzig tram network E735557 entity
Predicate operator P179 FINISHED
Object Leipziger Verkehrsbetriebe
Leipziger Verkehrsbetriebe is the municipal public transport company of Leipzig, Germany, responsible for operating the city’s tram and bus services.
E1848548 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: Leipziger Verkehrsbetriebe | Statement: [Leipzig tram network, operator, Leipziger Verkehrsbetriebe]
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: Leipziger Verkehrsbetriebe
Triple: [Leipzig tram network, operator, Leipziger Verkehrsbetriebe]
Generated description
Leipziger Verkehrsbetriebe is the municipal public transport company of Leipzig, Germany, responsible for operating the city’s tram and bus services.

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_69f077e85498819088b65186550da8cd completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f66097d3288190908ec88a1db6a3c0 completed May 2, 2026, 8:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a251f7fc754819089507f393d89947d completed June 7, 2026, 7:36 a.m.
NEDg Description generation batch_6a25239d75fc819097fecb8edcd63e80 completed June 7, 2026, 7:54 a.m.
NED2 Entity disambiguation (via description) batch_6a25283e68608190a5f0b319c8028258 completed June 7, 2026, 8:13 a.m.
Created at: April 28, 2026, 10:15 a.m.