Triple

T20159108
Position Surface form Disambiguated ID Type / Status
Subject Oberammergau E491655 entity
Predicate hasNearbyMountain P651 FINISHED
Object Kofel NE NERFINISHED

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: Kofel | Statement: [Oberammergau, hasNearbyMountain, Kofel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kofel
Context triple: [Oberammergau, hasNearbyMountain, Kofel]
  • A. Kofel chosen
    Kofel is a distinctive, steep limestone peak overlooking the town of Oberammergau in the Ammergau Alps of Bavaria, Germany, popular with hikers and climbers.
  • B. Schrankogel
    Schrankogel is one of the highest and most prominent mountains in the Stubai Alps of Tyrol, Austria, popular with experienced alpine climbers.
  • C. Bärenkopf
    Bärenkopf is a mountain peak in the Austrian Alps that forms part of the Glockner Group.
  • D. Brennkogel
    Brennkogel is a mountain peak in the Austrian Alps, located within the Glockner Group of the High Tauern range.
  • E. Wendelstein mountain
    Wendelstein mountain is a prominent peak in the Bavarian Alps of southern Germany, known for its panoramic views, observatory, and historic cogwheel railway.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e667e27aa88190a326288b992ea274 completed April 20, 2026, 5:52 p.m.
Created at: April 11, 2026, 11:34 p.m.