Triple

T8679223
Position Surface form Disambiguated ID Type / Status
Subject Theobald E205990 entity
Predicate hasVariantForm P457 FINISHED
Object Tybalt E287850 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: Tybalt | Statement: [Theobald, hasVariantForm, Tybalt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tybalt
Context triple: [Theobald, hasVariantForm, Tybalt]
  • A. Tybalt chosen
    Tybalt is a hot-headed and aggressive Capulet nobleman in Shakespeare’s "Romeo and Juliet," known for his hatred of the Montagues and his pivotal role in escalating the feud.
  • B. Mercutio
    Mercutio is a witty, charismatic nobleman and close companion of Romeo in Shakespeare’s tragedy "Romeo and Juliet," known for his sharp tongue and tragic fate.
  • C. Lord Montague
    Lord Montague is the patriarch of the Montague family in Shakespeare's "Romeo and Juliet," serving as Romeo's father and a central figure in the feud with the Capulets.
  • D. Benvolio
    Benvolio is a peace-loving and loyal friend of Romeo in Shakespeare's tragedy "Romeo and Juliet," often trying to defuse conflicts between the feuding families.
  • E. Bernardo Morando
    Bernardo Morando was a 16th-century Italian architect best known for designing the Renaissance ideal city of Zamość in Poland.
  • 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_69ca835379688190aa06b9d98e684d58 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc49f8fa948190a070e90d17b4ede2 completed March 31, 2026, 10:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69cef3a98ee881908d546e9a55217792 completed April 2, 2026, 10:54 p.m.
Created at: March 30, 2026, 6:32 p.m.