Triple

T35542232
Position Surface form Disambiguated ID Type / Status
Subject Paradeplatz E1027090 entity
Predicate servedByTramLine P17788 FINISHED
Object Tram line 13
Tram line 13 is a public transport route in Zürich’s tram network, connecting various city districts and key central stops as part of the Zürich Verkehrsbetriebe (VBZ) system.
E2145268 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: Tram line 13 | Statement: [Paradeplatz, servedByTramLine, Tram line 13]
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: Tram line 13
Triple: [Paradeplatz, servedByTramLine, Tram line 13]
Generated description
Tram line 13 is a public transport route in Zürich’s tram network, connecting various city districts and key central stops as part of the Zürich Verkehrsbetriebe (VBZ) system.

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_69f76e008ba08190927acd8e5e0344c8 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79806ab6c81909cddc30ac63ca80e completed May 3, 2026, 6:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3852eb5ee881909aecfe7cb3add09a completed June 21, 2026, 9:08 p.m.
NEDg Description generation batch_6a38537cefd48190b5d223a5506b4f2d completed June 21, 2026, 9:11 p.m.
NED2 Entity disambiguation (via description) batch_6a38546765988190bba6f0bc046274df completed June 21, 2026, 9:15 p.m.
Created at: May 3, 2026, 4:04 p.m.