Triple

T20376205
Position Surface form Disambiguated ID Type / Status
Subject Sellano E497698 entity
Predicate locatedNear P294 FINISHED
Object Foligno 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: Foligno | Statement: [Sellano, locatedNear, Foligno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Foligno
Context triple: [Sellano, locatedNear, Foligno]
  • A. Foligno chosen
    Foligno is a historic city in central Italy known for its medieval architecture, cultural festivals, and strategic location along the Via Flaminia.
  • B. Grignone
    Grignone is the higher, more prominent summit of the Grigna massif in the Lombardy region of northern Italy, popular with hikers and climbers for its panoramic Alpine views.
  • C. Suzzara
    Suzzara is a town and comune in the Lombardy region of northern Italy, known for its industrial activity and location near the Po River.
  • D. Schio
    Schio is an industrial town in northeastern Italy known historically for its textile production and location in the Veneto region.
  • E. Pioltello
    Pioltello is a municipality in the Metropolitan City of Milan in Lombardy, northern Italy, known as a residential and industrial suburb of Milan.
  • 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_69e0b4a5b7908190a972e4e7e698ae94 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e678ad74348190ac57d38eaa56beb3 completed April 20, 2026, 7:04 p.m.
Created at: April 16, 2026, 11:27 a.m.