Triple

T20019094
Position Surface form Disambiguated ID Type / Status
Subject Devine E494801 entity
Predicate hasVariant P455 FINISHED
Object Devane 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: Devane | Statement: [Devine, hasVariant, Devane]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Devane
Context triple: [Devine, hasVariant, Devane]
  • A. Devane chosen
    Devane is a surname most notably associated with American actor William Devane, known for his roles in film and television dramas.
  • B. Devine
    Devine is a surname of Irish origin borne by various notable individuals across fields such as sports, politics, and the arts.
  • C. Donoven
    Donoven is an alternative spelling of the given name Donovan, which is of Irish origin and used as a masculine first name and surname.
  • D. Devorski
    Devorski is a surname most notably associated with Paul Devorski, a former National Hockey League referee.
  • E. Deneen
    Deneen is a surname most notably associated with Charles S. Deneen, an American politician who served as governor of Illinois and later as a U.S. senator.
  • 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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6623e40748190b1abb0ead9acab4e completed April 20, 2026, 5:28 p.m.
Created at: April 11, 2026, 3:34 p.m.