Triple

T22115264
Position Surface form Disambiguated ID Type / Status
Subject Teatro di corte in Mantua E546524 entity
Predicate locatedIn P40 FINISHED
Object Mantua 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: Mantua | Statement: [Teatro di corte in Mantua, locatedIn, Mantua]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mantua
Context triple: [Teatro di corte in Mantua, locatedIn, Mantua]
  • A. Mantua chosen
    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.
  • B. Mantua
    Mantua is a residential neighborhood in West Philadelphia known for its historic rowhouses and proximity to major universities and cultural institutions.
  • C. Mantua
    Mantua is a small Cuban town and municipality located in the western part of Pinar del Río Province.
  • D. Verona
    Verona is a historic city in northern Italy renowned for its well-preserved Roman architecture and its association with Shakespeare’s "Romeo and Juliet."
  • E. Verona
    Verona is a small borough in Allegheny County, Pennsylvania, situated along the Allegheny River just northeast of Pittsburgh.
  • 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1294c5f908190bdb1cce3cbf86d85 completed April 28, 2026, 9:40 p.m.
Created at: April 16, 2026, 8:31 p.m.