Triple

T32584996
Position Surface form Disambiguated ID Type / Status
Subject Heraclid dynasty of Corinth E832896 entity
Predicate sharesMythicAncestorWith P18399 FINISHED
Object Heraclid dynasty of Sparta 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: Heraclid dynasty of Sparta | Statement: [Heraclid dynasty of Corinth, sharesMythicAncestorWith, Heraclid dynasty of Sparta]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesMythicAncestorWith
Context triple: [Heraclid dynasty of Corinth, sharesMythicAncestorWith, Heraclid dynasty of Sparta]
  • A. hasMythicAncestor
    Indicates that an entity is descended from, or claims lineage through, a figure from myth or legend.
  • B. sharesMythosWith
    Indicates that two entities are associated with, or originate from, the same mythological tradition, narrative system, or shared set of myths.
  • C. ancestralLinks
    Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
  • D. sharesCommonAncestorWith chosen
    Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
  • E. hasTribalAncestor
    Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
  • 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_69f349289adc81909f4374a58ec35a39 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ff5f5ecc808190b2df364da108ff4c completed May 9, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69ff5b84131c8190bf81d7fb53e934bc completed May 9, 2026, 4:06 p.m.
Created at: May 1, 2026, 1:04 a.m.