Triple

T19484836
Position Surface form Disambiguated ID Type / Status
Subject Bormida E487483 entity
Predicate hasPart P35 FINISHED
Object Bormida di Spigno 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: Bormida di Spigno | Statement: [Bormida, hasPart, Bormida di Spigno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bormida di Spigno
Context triple: [Bormida, hasPart, Bormida di Spigno]
  • A. Schignano
    Schignano is a small Italian village in the Lombardy region, known for its traditional Alpine setting and historic Carnival celebrations.
  • B. Bignasco
    Bignasco is a small village in the canton of Ticino in southern Switzerland, known for its Alpine setting in the Maggia Valley.
  • C. Borgotaro
    Borgotaro is a town and municipality in the Emilia-Romagna region of northern Italy, known for its surrounding Apennine landscapes and prized porcini mushrooms.
  • D. Bormida chosen
    Bormida is a river in northwestern Italy that flows through the regions of Piedmont and Liguria before joining the Tanaro.
  • E. Bompietro
    Bompietro is a small municipality in Sicily, Italy, known for its rural character and location in the hilly interior of the island.
  • 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6343dcc748190b0df816e6ab4cafb completed April 20, 2026, 2:12 p.m.
Created at: April 10, 2026, 1:39 p.m.