Triple

T11869222
Position Surface form Disambiguated ID Type / Status
Subject Schwyz E282362 entity
Predicate contains P35 FINISHED
Object Brunnen E528286 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: Brunnen | Statement: [Schwyz, contains, Brunnen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brunnen
Context triple: [Schwyz, contains, Brunnen]
  • A. Brunnen chosen
    Brunnen is a Swiss lakeside village on Lake Lucerne in the canton of Schwyz, known for its scenic alpine setting and role as a popular tourist destination.
  • B. Feldbrunnen
    Feldbrunnen is a village and municipality in the canton of Solothurn in northwestern Switzerland.
  • C. Neptunbrunnen
    Neptunbrunnen is a historic fountain in central Berlin featuring a monumental statue of Neptune surrounded by allegorical figures representing major German rivers.
  • D. Schängelbrunnen
    Schängelbrunnen is a famous bronze fountain in Koblenz, Germany, depicting a mischievous boy and symbolizing the city's local identity and dialect.
  • E. Elisenbrunnen
    Elisenbrunnen is a historic neoclassical spa pavilion in Aachen, Germany, renowned for its sulfurous thermal springs and role as a symbol of the city’s spa culture.
  • 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_69d6ab2945d081908a5851c916cbcfb5 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a73c04e4819084c0b2ff8e5d2f04 completed April 10, 2026, 7:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69f281a2abfc8190a4769e637dedaaab completed April 29, 2026, 10:09 p.m.
Created at: April 8, 2026, 9:43 p.m.