Triple

T9501142
Position Surface form Disambiguated ID Type / Status
Subject Province of Milan E229141 entity
Predicate contains P35 FINISHED
Object Legnano E329532 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: Legnano | Statement: [Province of Milan, contains, Legnano]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Legnano
Context triple: [Province of Milan, contains, Legnano]
  • A. Legnano chosen
    Legnano is a town in the Lombardy region of northern Italy, historically known for its medieval Battle of Legnano and its industrial development.
  • B. Cassano d’Adda
    Cassano d’Adda is a town in the Lombardy region of northern Italy, situated along the Adda River northeast of Milan.
  • C. Saronno
    Saronno is an Italian town in Lombardy known for its traditional amaretto liqueur and almond-flavored confections.
  • D. Busto Arsizio
    Busto Arsizio is an industrial city in the Lombardy region of northern Italy, known for its textile and manufacturing heritage and its location within the greater Milan metropolitan area.
  • E. Melegnano
    Melegnano is a town in the Lombardy region of northern Italy, historically notable as the site of major Renaissance-era battles including the Battle of Marignano.
  • 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_69ca84753660819098e8d416e89e26ae completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd983d4b708190a4dfef1246986a26 completed April 1, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69d29999e9248190b2f1900fa7ad3da5 completed April 5, 2026, 5:19 p.m.
Created at: March 30, 2026, 7:57 p.m.