Triple

T31174398
Position Surface form Disambiguated ID Type / Status
Subject Nuremberg Plärrer E794701 entity
Predicate hasRoadConnection P385 FINISHED
Object Fürther Straße
Fürther Straße is a major arterial road in Nuremberg, Germany, connecting the city center with the neighboring city of Fürth and serving as an important commercial and traffic route.
E2092513 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: Fürther Straße | Statement: [Nuremberg Plärrer, hasRoadConnection, Fürther Straße]
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: Fürther Straße
Triple: [Nuremberg Plärrer, hasRoadConnection, Fürther Straße]
Generated description
Fürther Straße is a major arterial road in Nuremberg, Germany, connecting the city center with the neighboring city of Fürth and serving as an important commercial and traffic route.

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_69f224d5b9708190b6ca79ad2fd3a28a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f698b3e96081909996ecea317507a4 completed May 3, 2026, 12:37 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3704765f208190a18f228355529365 completed June 20, 2026, 9:21 p.m.
NEDg Description generation batch_6a370577d8e08190848ce63a9865793d completed June 20, 2026, 9:26 p.m.
NED2 Entity disambiguation (via description) batch_6a37061b69fc81908c02244b45d74771 completed June 20, 2026, 9:28 p.m.
Created at: April 29, 2026, 9:07 p.m.