Triple

T16706590
Position Surface form Disambiguated ID Type / Status
Subject Novilara E405985 entity
Predicate partOf P40 FINISHED
Object Comune of Pesaro E693461 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: Comune of Pesaro | Statement: [Novilara, partOf, Comune of Pesaro]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Comune of Pesaro
Context triple: [Novilara, partOf, Comune of Pesaro]
  • A. Comune di Pesaro chosen
    Comune di Pesaro is the municipal government authority responsible for administering the city of Pesaro in Italy.
  • B. Municipality of Ancona
    The Municipality of Ancona is the local government authority responsible for administering the city of Ancona on Italy’s Adriatic coast.
  • C. Comune of La Spezia
    The Comune of La Spezia is a coastal municipality in the Liguria region of northwestern Italy, known for its important naval base, harbor, and proximity to the Cinque Terre.
  • D. Comune di Massa
    Comune di Massa is the municipal government and administrative body responsible for managing public services, local policies, and civic administration in the city of Massa, Italy.
  • E. Comune di Loreto
    Comune di Loreto is the municipal government authority responsible for administering the town of Loreto in Italy.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3833695908190afd4d2ece233be00 completed April 18, 2026, 1:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0091a36a5c8190a1486fcf11995b7c completed May 10, 2026, 2:09 p.m.
Created at: April 10, 2026, 5:19 a.m.