Triple

T7399101
Position Surface form Disambiguated ID Type / Status
Subject Ponte Bianco E170699 entity
Predicate hasNameInLanguage P15 FINISHED
Object Ponte Bianco (Italian) E170699 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 Bianco (Italian) | Statement: [Ponte Bianco, hasNameInLanguage, Ponte Bianco (Italian)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ponte Bianco (Italian)
Context triple: [Ponte Bianco, hasNameInLanguage, Ponte Bianco (Italian)]
  • A. Ponte Bianco chosen
    Ponte Bianco is a bridge in Trieste, Italy, spanning the city’s Canal Grande and connecting parts of its historic center.
  • B. Ponte di Legno
    Ponte di Legno is an Italian alpine town and ski resort in Lombardy, known for its mountain scenery and outdoor sports tourism.
  • C. Ponte
    Ponte is a Spanish-language surname of Iberian origin borne by various notable figures, including members of the Bolívar family.
  • D. Ponte Rosso
    Ponte Rosso is a historic bridge in Trieste, Italy, spanning the Canal Grande in the city’s central district.
  • E. Ponte Molle
    Ponte Molle is an alternative historical name for Ponte Milvio, a famous ancient bridge in Rome known for its strategic and cultural significance.
  • 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_69c68a5f04188190ac266569c9280347 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f24c1c208190a3d11e816888760d completed March 27, 2026, 9:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69c81106c0788190a3740acf7bb4ab86 completed March 28, 2026, 5:33 p.m.
Created at: March 27, 2026, 3:09 p.m.