Triple

T14222242
Position Surface form Disambiguated ID Type / Status
Subject Forum of Swiss History Schwyz E352525 entity
Predicate locatedIn P40 FINISHED
Object Schwyz E282362 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: Schwyz | Statement: [Forum of Swiss History Schwyz, locatedIn, Schwyz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schwyz
Context triple: [Forum of Swiss History Schwyz, locatedIn, Schwyz]
  • A. Schwyz chosen
    Schwyz is a historic canton in central Switzerland, known as one of the founding members that gave the Swiss Confederation its name.
  • B. Hergiswil
    Hergiswil is a Swiss lakeside municipality known for its scenic setting on Lake Lucerne and its historic glassworks.
  • C. Schaffhausen
    Schaffhausen is a historic town and capital of the canton of the same name in northern Switzerland, known for its well-preserved medieval old town and proximity to the Rhine Falls.
  • D. Luzern
    Luzern is a picturesque Swiss city on Lake Lucerne, renowned for its preserved medieval architecture, iconic Chapel Bridge, and surrounding mountain scenery.
  • E. Solothurn
    Solothurn is a canton in northwestern Switzerland known for its historic baroque town of the same name and its location along the Aare River.
  • 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_69d8278a06e481908b5d6af0a8afe737 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6227c288819081473ce44f9f0934 completed April 14, 2026, 3:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff2ce36ce08190930e791e2837d1a5 completed May 9, 2026, 12:47 p.m.
Created at: April 10, 2026, 1:06 a.m.