Triple

T30916093
Position Surface form Disambiguated ID Type / Status
Subject Uber Eats Music Hall (Berlin) E787582 entity
Predicate locatedIn P40 FINISHED
Object Mercedes-Platz
Mercedes-Platz is a modern entertainment and event district in Berlin featuring venues, restaurants, and leisure facilities near the Mercedes-Benz Arena.
E1998383 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: Mercedes-Platz | Statement: [Uber Eats Music Hall (Berlin), locatedIn, Mercedes-Platz]
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: Mercedes-Platz
Triple: [Uber Eats Music Hall (Berlin), locatedIn, Mercedes-Platz]
Generated description
Mercedes-Platz is a modern entertainment and event district in Berlin featuring venues, restaurants, and leisure facilities near the Mercedes-Benz Arena.

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_69f224be300c8190a6513ce1ee0a7026 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f692b251048190ba55b32cac9caf7a completed May 3, 2026, 12:11 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2f3b5ece40819097b7d1e28412b799 completed June 14, 2026, 11:38 p.m.
NEDg Description generation batch_6a2f3c951b4081909f5e3ca87783442f completed June 14, 2026, 11:43 p.m.
NED2 Entity disambiguation (via description) batch_6a2f4158e32c8190bac1224cb21b0247 completed June 15, 2026, 12:03 a.m.
Created at: April 29, 2026, 8:51 p.m.