Triple

T10163962
Position Surface form Disambiguated ID Type / Status
Subject Arno E233959 entity
Predicate hasBridge P386 FINISHED
Object Ponte alla Carraia E573181 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: Ponte alla Carraia | Statement: [Arno, hasBridge, Ponte alla Carraia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ponte alla Carraia
Context triple: [Arno, hasBridge, Ponte alla Carraia]
  • A. Ponte alla Carraia chosen
    Ponte alla Carraia is a historic multi-arched stone bridge in Florence, Italy, notable as one of the city’s oldest crossings over the Arno.
  • B. Ponte Santa Trinita
    Ponte Santa Trinita is a historic Renaissance bridge in Florence, Italy, renowned for its elegant elliptical arches and artistic significance.
  • C. Ponte Rosso
    Ponte Rosso is a historic bridge in Trieste, Italy, spanning the Canal Grande in the city’s central district.
  • D. Ponte Azzone Visconti
    Ponte Azzone Visconti is a historic multi-arched stone bridge in Lecco, Italy, dating back to the Middle Ages and notable for its strategic and architectural significance.
  • E. Ponte Sisto
    Ponte Sisto is a historic Renaissance pedestrian bridge in Rome that links the Trastevere district with the city center across the Tiber River.
  • 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_69ca848e80748190b91d1e04d35512c7 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec6a7bb48190952f4318af9cc32b completed April 2, 2026, 4:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d31774617c8190848ad4990fe5801d completed April 6, 2026, 2:16 a.m.
Created at: March 30, 2026, 9:09 p.m.