Triple

T14020837
Position Surface form Disambiguated ID Type / Status
Subject Livornese dialect E337324 entity
Predicate spokenIn P2266 FINISHED
Object Livorno E67624 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: Livorno | Statement: [Livornese dialect, spokenIn, Livorno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Livorno
Context triple: [Livornese dialect, spokenIn, Livorno]
  • A. Livorno chosen
    Livorno is a port city on Italy’s western coast, historically notable for its diverse communities and significant Jewish population.
  • B. Livorno
    Livorno is a settlement in Wanica District, Suriname, known as a suburban community near the capital city of Paramaribo.
  • C. La Spezia
    La Spezia is a port city in northwestern Italy known as a major naval base and gateway to the Cinque Terre on the Ligurian coast.
  • D. San Leo
    San Leo is a historic hilltop town in Italy’s Emilia-Romagna region, renowned for its imposing fortress and panoramic views over the Marecchia Valley.
  • E. Savona
    Savona is a coastal city and port in the Liguria region of northwestern Italy, known historically as a strategic maritime center on the Italian Riviera.
  • 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_69d81c6543a48190bd5ba93d7419e797 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2f3c7cd88190b236382058581740 completed April 14, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd324133f8819088c0d80a4e8fb5be completed May 8, 2026, 12:45 a.m.
Created at: April 9, 2026, 10:19 p.m.