Triple

T340523
Position Surface form Disambiguated ID Type / Status
Subject Tridentine Cathedral E6825 entity
Predicate locatedIn P40 FINISHED
Object Trento E17477 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: Trento | Statement: [Tridentine Cathedral, locatedIn, Trento]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trento
Context triple: [Tridentine Cathedral, locatedIn, Trento]
  • A. Trento chosen
    Trento is a historic city in northern Italy, known as the capital of Trentino and for its significant role in Catholic history and Alpine culture.
  • B. Padua
    Padua is a historic city in northern Italy renowned as a major cultural and academic center, home to one of Europe’s oldest universities.
  • C. Lecco
    Lecco is an Italian town in the Lombardy region, known for its scenic location at the southeastern tip of Lake Como and its surrounding Alpine foothills.
  • D. Vicenza
    Vicenza is a historic city in northeastern Italy renowned for its Palladian architecture and cultural heritage.
  • E. Mantua
    Mantua is a historic city in northern Italy’s Lombardy region, renowned for its Renaissance architecture, artistic heritage, and former status as the seat of the Gonzaga dynasty.
  • 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_69a2e7951ba08190960e90823b5078f3 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eae4fcc08190bd4c2bf0149c8b50 completed Feb. 28, 2026, 1:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4fc783c948190bc61a51fc3e3ff1f completed March 2, 2026, 2:56 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.