Triple

T8599658
Position Surface form Disambiguated ID Type / Status
Subject Francesco Sforza E203642 entity
Predicate familyName P18 FINISHED
Object Sforza E631644 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: Sforza | Statement: [Francesco Sforza, familyName, Sforza]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sforza
Context triple: [Francesco Sforza, familyName, Sforza]
  • A. Sforza chosen
    Sforza is the name of a powerful Italian Renaissance noble family that ruled Milan and produced influential political and military leaders.
  • B. Francesco Sforza
    Francesco Sforza was a 15th-century Italian condottiero who became Duke of Milan and founded the Sforza dynasty, playing a key role in the politics of Renaissance Italy.
  • C. Giovanni Sforza
    Giovanni Sforza was an Italian nobleman and lord of Pesaro, best known as the first husband of Lucrezia Borgia and for his politically charged annulled marriage to her.
  • D. Ludovico Sforza
    Ludovico Sforza was a Renaissance-era Duke of Milan best known as a powerful patron of the arts, particularly of Leonardo da Vinci.
  • E. Duke Galeazzo Maria Sforza
    Duke Galeazzo Maria Sforza was a 15th-century Duke of Milan from the powerful Sforza dynasty, known for his lavish court, political intrigue, and eventual assassination.
  • 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_69ca832b56948190ba751cec255308f1 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46d7c184819083236c75f9ccc9cf completed March 31, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf425243d8819084af0a789c73ea7c completed April 3, 2026, 4:30 a.m.
Created at: March 30, 2026, 6:24 p.m.