Triple

T30882234
Position Surface form Disambiguated ID Type / Status
Subject Tauentzienstraße E786649 entity
Predicate hasPublicTransportConnection P3791 FINISHED
Object U3 Berlin U-Bahn line
The U3 Berlin U-Bahn line is a metro line in Berlin that runs primarily through the southwestern districts, connecting central hubs with residential and university areas.
E1950266 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: U3 Berlin U-Bahn line | Statement: [Tauentzienstraße, hasPublicTransportConnection, U3 Berlin U-Bahn line]
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: U3 Berlin U-Bahn line
Triple: [Tauentzienstraße, hasPublicTransportConnection, U3 Berlin U-Bahn line]
Generated description
The U3 Berlin U-Bahn line is a metro line in Berlin that runs primarily through the southwestern districts, connecting central hubs with residential and university areas.

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_69f224bae17c8190bb3a6a28e3d019df completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6920337108190be9cbe5d90986f5c completed May 3, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a294705abd8819087b8f8f227de21b7 completed June 10, 2026, 11:14 a.m.
NEDg Description generation batch_6a294edd87888190a40f71d4d7f57b18 completed June 10, 2026, 11:47 a.m.
NED2 Entity disambiguation (via description) batch_6a2950ac30e88190a3f55d5a68f317d8 completed June 10, 2026, 11:55 a.m.
Created at: April 29, 2026, 8:48 p.m.