Triple

T9384321
Position Surface form Disambiguated ID Type / Status
Subject Genoese lira E225866 entity
Predicate usedIn P98 FINISHED
Object Genoa E19522 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: Genoa | Statement: [Genoese lira, usedIn, Genoa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Genoa
Context triple: [Genoese lira, usedIn, Genoa]
  • A. Genoa chosen
    Genoa is a historic port city in northwestern Italy known for its significant maritime heritage, trade, and role as a major economic hub on the Ligurian coast.
  • B. Genoa
    Genoa is the codename for AMD’s fourth-generation EPYC server processors based on the Zen 4 architecture and the SP5 platform.
  • C. Port of Genoa
    The Port of Genoa is one of Italy’s largest and busiest seaports, serving as a major hub for commercial shipping, passenger ferries, and maritime trade in the Mediterranean.
  • D. Livorno
    Livorno is a port city on Italy’s western coast, historically notable for its diverse communities and significant Jewish population.
  • 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_69ca842e9dcc8190a264119e683cfe04 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd50c23e7881908112597a1771afa5 completed April 1, 2026, 5:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1101e83e8819093fe8d25c819820b completed April 4, 2026, 1:20 p.m.
Created at: March 30, 2026, 7:44 p.m.