Triple

T18941943
Position Surface form Disambiguated ID Type / Status
Subject ISO 3166-2:SM E463403 entity
Predicate definesSubdivision P747 FINISHED
Object Domagnano 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: Domagnano | Statement: [ISO 3166-2:SM, definesSubdivision, Domagnano]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Domagnano
Context triple: [ISO 3166-2:SM, definesSubdivision, Domagnano]
  • A. Domagnano chosen
    Domagnano is one of the nine municipalities (castelli) of San Marino, located in the northeastern part of the country.
  • B. Orzinuovi
    Orzinuovi is a town and comune in the province of Brescia in the Lombardy region of northern Italy.
  • C. Solignano
    Solignano is a small municipality in the Province of Parma in Italy’s Emilia-Romagna region, known for its rural landscape and location in the Taro Valley.
  • D. Lavagnesi
    Lavagnesi are the inhabitants or natives of Lavagna, a coastal town in the Liguria region of northwestern Italy.
  • E. Pontremoli
    Pontremoli is a historic town in northern Tuscany, Italy, known for its medieval architecture and strategic location along the ancient Via Francigena pilgrimage route.
  • 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_69d8dcfec90481909e926be9767e5779 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d3ec857081908da0f974604f2c65 completed April 20, 2026, 7:21 a.m.
Created at: April 10, 2026, 11:59 a.m.