Triple

T4711117
Position Surface form Disambiguated ID Type / Status
Subject Adda E104512 entity
Predicate crossesCity P13729 FINISHED
Object Lecco E35247 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: Lecco | Statement: [Adda, crossesCity, Lecco]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lecco
Context triple: [Adda, crossesCity, Lecco]
  • A. Lecco chosen
    Lecco is an Italian town in the Lombardy region, known for its scenic location at the southeastern tip of Lake Como and its surrounding Alpine foothills.
  • B. Varese
    Varese is a city in northern Italy known for its lakeside setting, surrounding Prealps, and role as an important economic and cultural center in the Lombardy region.
  • C. 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.
  • D. Bergamo
    Bergamo is a historic city in northern Italy known for its medieval walled upper town, rich artistic heritage, and strategic location at the foothills of the Alps.
  • E. Legnano
    Legnano is a town in the Lombardy region of northern Italy, historically known for its medieval Battle of Legnano and its industrial development.
  • 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_69bd43eac3c08190af7e4020c6c3704c completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64049d6c8190be19935048fc6b14 completed March 20, 2026, 3:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69be922a8fc08190ad2dd4ffc1697f08 completed March 21, 2026, 12:42 p.m.
Created at: March 20, 2026, 1:17 p.m.