Triple

T23783038
Position Surface form Disambiguated ID Type / Status
Subject Theseus and the Crommyonian Sow E587868 entity
Predicate associatedHeroLineage P125063 FINISHED
Object son of Aegeus or Poseidon LITERAL FINISHED

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: son of Aegeus or Poseidon | Statement: [Theseus and the Crommyonian Sow, associatedHeroLineage, son of Aegeus or Poseidon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedHeroLineage
Context triple: [Theseus and the Crommyonian Sow, associatedHeroLineage, son of Aegeus or Poseidon]
  • A. basedOnCharacterLineage
    Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
  • B. linkedHero
    Indicates a relationship where one hero is associated or connected to another hero in a meaningful way.
  • C. lineageRelatedTo
    Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
  • D. associatedWithCharacterFamily chosen
    Indicates a relationship where something is linked or connected to a particular character’s family.
  • E. includesHeroes
    Indicates that something (such as a work, group, or collection) contains or features one or more heroes as part of it.
  • 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_69e2490f4ad48190b690878eec3596c6 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1c62ea9c0819083544822267d3215 completed April 29, 2026, 8:49 a.m.
PD Predicate disambiguation batch_69f155f79e34819080f9ddb972b34deb completed April 29, 2026, 12:51 a.m.
Created at: April 17, 2026, 7:16 p.m.