Triple

T11723938
Position Surface form Disambiguated ID Type / Status
Subject Segrate E278710 entity
Predicate borders P224 FINISHED
Object Cologno Monzese E805187 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: Cologno Monzese | Statement: [Segrate, borders, Cologno Monzese]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cologno Monzese
Context triple: [Segrate, borders, Cologno Monzese]
  • A. Cologno Monzese chosen
    Cologno Monzese is a suburban town in northern Italy known for hosting major television and media studios near Milan.
  • B. 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.
  • C. Olgiate Comasco
    Olgiate Comasco is a town and municipality in the Lombardy region of northern Italy, situated near the city of Como and close to the Swiss border.
  • D. Vergiate
    Vergiate is a town in the Lombardy region of northern Italy known for its significant aerospace and helicopter manufacturing facilities.
  • E. Bovisio-Masciago
    Bovisio-Masciago is a small municipality in the Lombardy region of northern Italy, situated in the Brianza area north of Milan.
  • 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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4d603cc8190b2e68d0bdd793362 completed April 10, 2026, 7:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69f4174972ac819094f3938b18a5081e completed May 1, 2026, 3 a.m.
Created at: April 8, 2026, 9:41 p.m.