Triple

T33413235
Position Surface form Disambiguated ID Type / Status
Subject Εὐμενίδες E855643 entity
Predicate hasTrilogyCompanionWorkEnglish P199420 FINISHED
Object Agamemnon 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: Agamemnon | Statement: [Εὐμενίδες, hasTrilogyCompanionWorkEnglish, Agamemnon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrilogyCompanionWorkEnglish
Context triple: [Εὐμενίδες, hasTrilogyCompanionWorkEnglish, Agamemnon]
  • A. hasTrilogy
    Indicates that an entity is part of, or associated with, a specific trilogy within a larger set of works or narratives.
  • B. hasCompanionBook
    Indicates that one entity (typically a primary work) is associated with another entity that serves as its companion book, providing supplementary or related content.
  • C. hasEnglishEdition
    Indicates that one entity has a version or edition of itself that is produced or available in the English language.
  • D. hasPartInTrilogy
    Indicates that an entity is one of the constituent parts (e.g., books, films, or episodes) that together form a specific trilogy.
  • E. hasSequelInTrilogy
    Indicates that one work in a trilogy is followed by another work that serves as its sequel within that same three-part series.
  • F. None of above. chosen

Provenance (4 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_69f3496f04a08190804e56ac5098b8e4 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff38b960808190a8263348f1e5c0e4 completed May 9, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69ff37d97d9c8190849b2bac14f9af1d completed May 9, 2026, 1:34 p.m.
PDg Predicate description generation batch_69ff38b8843c819097359a4d77e9d442 completed May 9, 2026, 1:38 p.m.
Created at: May 1, 2026, 1:36 a.m.