Triple

T20747965
Position Surface form Disambiguated ID Type / Status
Subject Ponte E510637 entity
Predicate hasVariant P455 FINISHED
Object da Ponte 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: da Ponte | Statement: [Ponte, hasVariant, da Ponte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: da Ponte
Context triple: [Ponte, hasVariant, da Ponte]
  • A. Ponte chosen
    Ponte is a Spanish-language surname of Iberian origin borne by various notable figures, including members of the Bolívar family.
  • B. Ponte
    Ponte is a small locality that forms one of the subdivisions (frazioni) of the municipality of Cerreto di Spoleto in the Umbria region of central Italy.
  • C. Ponte del Diavolo
    Ponte del Diavolo is a medieval stone arch bridge in Tuscany, Italy, renowned for its striking asymmetrical arches and associated legends about a pact with the devil.
  • D. Lusoponte
    Lusoponte is a Portuguese concession company responsible for operating and maintaining major road bridges over the Tagus River in the Lisbon region.
  • E. Le Pont
    Le Pont is a small Swiss village in the Vallée de Joux, known for its scenic lakeside setting on the shores of Lac de Joux and its role as a local tourism and outdoor recreation hub.
  • 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_69e0b4c845e88190b4c5f3ae79291182 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c226fbf881909794eff3ee9e206b completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:33 p.m.