Triple

T29883365
Position Surface form Disambiguated ID Type / Status
Subject Munich Isartor station E758942 entity
Predicate hasEntranceFrom P1985 FINISHED
Object Zweibrückenstraße
Zweibrückenstraße is a street in central Munich that provides access to the Isartor S-Bahn station and connects to the surrounding inner-city road network.
E2054731 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: Zweibrückenstraße | Statement: [Munich Isartor station, hasEntranceFrom, Zweibrückenstraß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: Zweibrückenstraße
Triple: [Munich Isartor station, hasEntranceFrom, Zweibrückenstraße]
Generated description
Zweibrückenstraße is a street in central Munich that provides access to the Isartor S-Bahn station and connects to the surrounding inner-city road network.

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_69f2245de2f48190a481404896b56254 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f676fb3b9c819097dcd5920e0cd09e completed May 2, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a35a64b23ec8190938f1ae72efbec59 completed June 19, 2026, 8:27 p.m.
NEDg Description generation batch_6a35a6bf0bb08190878fe21fa3c6d5ea completed June 19, 2026, 8:29 p.m.
NED2 Entity disambiguation (via description) batch_6a35a731ae0c8190a71409322d9c5ad0 completed June 19, 2026, 8:31 p.m.
Created at: April 29, 2026, 5:58 p.m.