Triple

T21847236
Position Surface form Disambiguated ID Type / Status
Subject All for Love E539406 entity
Predicate mainCharacter P1183 FINISHED
Object Ventidius 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: Ventidius | Statement: [All for Love, mainCharacter, Ventidius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ventidius
Context triple: [All for Love, mainCharacter, Ventidius]
  • A. Ventidius chosen
    Ventidius is a Roman general and loyal supporter of Mark Antony who appears as a minor but significant character in William Shakespeare’s tragedy "Antony and Cleopatra."
  • B. Curius
    Curius is the Roman family name (nomen) associated with the notable statesman and general Manius Curius Dentatus.
  • C. Quintianus
    Quintianus is a Roman cognomen derived from the praenomen Quintus, typically indicating familial or ancestral association with someone bearing that name.
  • D. Aelius
    Aelius is an ancient Roman family name (nomen) associated with several notable figures of the Roman Empire, including emperors and high-ranking officials.
  • E. Paullus
    Paullus is a Roman praenomen (personal name) associated with the patrician gens Fabia in ancient Rome.
  • 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_69e0c476c3c88190a92d08ebb59a128a completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0bd558ed88190a10b8d6752105cd6 completed April 28, 2026, 1:59 p.m.
Created at: April 16, 2026, 6:55 p.m.