Triple

T2640109
Position Surface form Disambiguated ID Type / Status
Subject Isère E62843 entity
Predicate contains P35 FINISHED
Object Vienne E20467 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: Vienne | Statement: [Isère, contains, Vienne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vienne
Context triple: [Isère, contains, Vienne]
  • A. Vienne chosen
    Vienne is a historic town in southeastern France known for its well-preserved Roman and medieval heritage, including ancient temples, a Roman theater, and a Gothic cathedral.
  • B. Vienna
    Vienna is the capital city of Austria, renowned for its rich imperial history, classical music heritage, and vibrant cultural and intellectual life.
  • C. Vienna
    Vienna is a suburban town in Fairfax County, Virginia, known for its residential neighborhoods, proximity to Washington, D.C., and access to the Washington Metro via the nearby Vienna/Fairfax–GMU station.
  • D. Salzburg
    Salzburg is a historic Austrian city on the Salzach River, renowned for its baroque architecture, Alpine setting, and as the birthplace of composer Wolfgang Amadeus Mozart.
  • E. Linz
    Linz is a major Austrian city known for its industrial heritage, vibrant cultural scene, and location along the Danube 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_69ab4c3f2dcc819082df80f5e032f690 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abd8fc8ee881908a9f6820d8934a62 completed March 7, 2026, 7:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69b01d3d6a54819090068ef1807ca921 completed March 10, 2026, 1:31 p.m.
Created at: March 6, 2026, 9:53 p.m.