Triple

T13515358
Position Surface form Disambiguated ID Type / Status
Subject Province of Ancona E322745 entity
Predicate contains P35 FINISHED
Object Jesi E236618 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: Jesi | Statement: [Province of Ancona, contains, Jesi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jesi
Context triple: [Province of Ancona, contains, Jesi]
  • A. Jesi chosen
    Jesi is a historic town in Italy’s Marche region, known as the birthplace of Holy Roman Emperor Frederick II and for its well-preserved medieval architecture.
  • B. Jastarnia
    Jastarnia is a seaside resort town and fishing port on Poland’s Baltic coast, popular for its beaches and water sports.
  • C. Jaru
    Jaru is a municipality in the Brazilian state of Rondônia, located in the northern region of the country within the Amazon basin.
  • D. Olecko
    Olecko is a small town in northeastern Poland known for its lakeside setting and location within the historic region of Masuria.
  • E. Jauru
    Jauru is an alternative name for the Yawuru, an Aboriginal Australian people traditionally associated with the Broome region of Western Australia.
  • 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafa0ed508190b2855171b1945e84 completed April 12, 2026, 2:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75494642881909f33962afe26f427 completed May 3, 2026, 1:58 p.m.
Created at: April 9, 2026, 9:44 p.m.