Triple

T3305552
Position Surface form Disambiguated ID Type / Status
Subject Rosenheim E69439 entity
Predicate twinTown P1072 FINISHED
Object Briançon E309330 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: Briançon | Statement: [Rosenheim, twinTown, Briançon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Briançon
Context triple: [Rosenheim, twinTown, Briançon]
  • A. Briançon chosen
    Briançon is a fortified alpine town in southeastern France, known as one of the highest cities in Europe and a key historical stronghold near the Italian border.
  • B. Grenoble
    Grenoble is a major city in southeastern France, known for its Alpine setting, universities, and research centers.
  • C. Aix-les-Bains
    Aix-les-Bains is a French spa and resort town in the Savoie department, renowned for its thermal baths and lakeside setting on the edge of the Alps.
  • D. Chambéry
    Chambéry is a historic city in southeastern France that served as the political and cultural center of the former Duchy of Savoy.
  • E. Échirolles
    Échirolles is a suburban commune in southeastern France, forming part of the Grenoble metropolitan area in the Isère department.
  • 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_69ad859f218081909458d2cebbf57565 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb0c9470881908c36c1984fdbb67b completed March 8, 2026, 5:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69b51c5ab7988190882df3b8198ad88a completed March 14, 2026, 8:29 a.m.
Created at: March 8, 2026, 3:11 p.m.