Triple

T22718463
Position Surface form Disambiguated ID Type / Status
Subject Arsamene E561795 entity
Predicate hasRomanticInvolvementWith P61561 FINISHED
Object Romilda NE NERFINISHED

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: Romilda | Statement: [Arsamene, hasRomanticInvolvementWith, Romilda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Romilda
Context triple: [Arsamene, hasRomanticInvolvementWith, Romilda]
  • A. Romilda chosen
    Romilda is a principal female character in Handel’s opera "Serse," known for being the object of the title character’s romantic pursuit and for her own love for another man.
  • B. Rosalinda
    Rosalinda is a feminine given name of Spanish and Italian origin, often interpreted to mean "beautiful rose."
  • C. Romina
    Romina is an Italian-American actress and singer best known as half of the pop duo Al Bano & Romina Power.
  • D. Lillita
    Lillita is the birth name of Lita Grey, the American actress best known for her early silent film work and marriage to Charlie Chaplin.
  • E. Lucilla
    Lucilla was a Roman imperial princess and daughter of Emperor Marcus Aurelius who became Empress as the wife of Lucius Verus and was later implicated in a plot against her brother Commodus.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2454fc984819088213b58ee87a002 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1790fbf9c819082ba7b48801a7b39 completed April 29, 2026, 3:20 a.m.
Created at: April 17, 2026, 3:19 p.m.