Triple

T10130490
Position Surface form Disambiguated ID Type / Status
Subject Montefalco E226324 entity
Predicate near P350 FINISHED
Object Foligno E214235 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: Foligno | Statement: [Montefalco, near, Foligno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Foligno
Context triple: [Montefalco, near, 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. Schio
    Schio is an industrial town in northeastern Italy known historically for its textile production and location in the Veneto region.
  • D. Fermo
    Fermo is a historic hilltop city in Italy’s Marche region, known for its medieval architecture, Roman heritage, and panoramic views over the Adriatic coast.
  • E. Rieti
    Rieti is a historic town in central Italy often considered the geographical center of the country and known for its medieval architecture and proximity to the Apennine Mountains.
  • 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_69ca843057b48190a86730167f5d6b98 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cdd33438988190be45878f98695816 completed April 2, 2026, 2:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69d7947e14c88190b9e33e3fbdcc16e5 completed April 9, 2026, 11:58 a.m.
Created at: March 30, 2026, 9:05 p.m.