Triple

T34280155
Position Surface form Disambiguated ID Type / Status
Subject Holbeinstraße E879569 entity
Predicate hasNearbyStreet P8235 FINISHED
Object Stresemannallee
Stresemannallee is a major street in Frankfurt am Main, Germany, known for connecting the city center with the Sachsenhausen district and serving as an important urban traffic artery.
E2195521 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: Stresemannallee | Statement: [Holbeinstraße, hasNearbyStreet, Stresemannallee]
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: Stresemannallee
Triple: [Holbeinstraße, hasNearbyStreet, Stresemannallee]
Generated description
Stresemannallee is a major street in Frankfurt am Main, Germany, known for connecting the city center with the Sachsenhausen district and serving as an important urban traffic artery.

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_69f349b5f6648190b9420d94a4cd16e0 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f712ee4d1081909fae80a3a2c7d32c completed May 3, 2026, 9:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3a38008cf481909bbbc8ec96f393e7 completed June 23, 2026, 7:38 a.m.
NEDg Description generation batch_6a3a39f576748190b0cb18e8e85c59fb completed June 23, 2026, 7:47 a.m.
NED2 Entity disambiguation (via description) batch_6a3a3b877df4819095fde5dba8c3b324 completed June 23, 2026, 7:53 a.m.
Created at: May 1, 2026, 1:57 a.m.