Triple

T28528081
Position Surface form Disambiguated ID Type / Status
Subject Astyoche E721963 entity
Predicate hasCloseMythologicalAssociationWith P9595 FINISHED
Object Orestes 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: Orestes | Statement: [Astyoche, hasCloseMythologicalAssociationWith, Orestes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCloseMythologicalAssociationWith
Context triple: [Astyoche, hasCloseMythologicalAssociationWith, Orestes]
  • A. hasMythologicalInhabitant
    Indicates that a place or location is traditionally believed to be inhabited or occupied by a mythological being or creature.
  • B. linkedToMythology chosen
    Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
  • C. closelyAssociatedDeity
    Indicates a deity that is strongly connected or frequently linked to another entity, such as a person, place, object, or concept, through special association or significance.
  • D. hasMythologicalNamesake
    Indicates that one entity is named after, or shares its name with, a figure or element from mythology.
  • E. hasMythologicalBasis
    Indicates that something is founded on, derived from, or significantly influenced by a mythological story, figure, or tradition.
  • F. None of above.

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_69f01a5d7ec88190ada2d5be7c06c35d completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f73223675481908c1bc3208c0f5284 completed May 3, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69f7317690108190b3aae2cd2e1d069e completed May 3, 2026, 11:28 a.m.
Created at: April 28, 2026, 3:26 a.m.