Triple

T4163169
Position Surface form Disambiguated ID Type / Status
Subject U3 E91577 entity
Predicate hasStation P35 FINISHED
Object Gustav-Adolf-Straße E444782 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: Gustav-Adolf-Straße | Statement: [U3, hasStation, Gustav-Adolf-Straße]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gustav-Adolf-Straße
Context triple: [U3, hasStation, Gustav-Adolf-Straße]
  • A. Gustav-Adolf-Straße chosen
    Gustav-Adolf-Straße is a subway station that serves as a terminus on Munich’s U3 line.
  • B. Gneisenaustraße
    Gneisenaustraße is a Berlin U-Bahn station on line U7 located in the Kreuzberg district.
  • C. Friedrichstraße
    Friedrichstraße is a major central Berlin transport hub and historic thoroughfare known for its shopping, cultural venues, and role as a former border crossing during the Cold War.
  • D. Schwartzkopffstraße
    Schwartzkopffstraße is a Berlin U-Bahn station on the U6 line located in the central district of the city.
  • E. Kaufingerstraße
    Kaufingerstraße is one of Munich’s main and oldest pedestrian shopping streets, lined with stores and historic buildings in the city center.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69aed9626ebc8190a39de631788bea3e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af02a811608190aff8b663498711e8 completed March 9, 2026, 5:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69b6721847ec8190bc4307ee958d1096 completed March 15, 2026, 8:47 a.m.
Created at: March 9, 2026, 3:44 p.m.