Triple

T21659345
Position Surface form Disambiguated ID Type / Status
Subject Buthier E534551 entity
Predicate flowsThrough P225 FINISHED
Object Aosta 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: Aosta | Statement: [Buthier, flowsThrough, Aosta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aosta
Context triple: [Buthier, flowsThrough, Aosta]
  • A. Aosta chosen
    Aosta is a historic town in northwestern Italy known as the capital of the Aosta Valley region and for its well-preserved Roman and medieval architecture.
  • B. Piossasco
    Piossasco is a municipality in the Metropolitan City of Turin in the Piedmont region of northwestern Italy.
  • C. Cherasco
    Cherasco is a historic town in Italy’s Piedmont region, known for its medieval architecture, strategic hilltop location, and proximity to renowned wine-producing areas such as Barolo.
  • D. Chieri
    Chieri is a historic town and comune in the Piedmont region of northwestern Italy, known for its medieval architecture and proximity to the city of Turin.
  • E. Chiavenna
    Chiavenna is a historic town in the Lombardy region of northern Italy, known for its alpine setting, medieval architecture, and role as a gateway to important mountain passes.
  • 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_69e0c467e1f48190af2650b19175abc4 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef6c06844c81909b9c91e02fa4e6e1 completed April 27, 2026, 2 p.m.
Created at: April 16, 2026, 6:36 p.m.