Triple

T22557320
Position Surface form Disambiguated ID Type / Status
Subject Althaemenes E557721 entity
Predicate actionTakenRegardingProphecy P67059 FINISHED
Object left Crete to avoid killing his father 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: left Crete to avoid killing his father | Statement: [Althaemenes, actionTakenRegardingProphecy, left Crete to avoid killing his father]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: actionTakenRegardingProphecy
Context triple: [Althaemenes, actionTakenRegardingProphecy, left Crete to avoid killing his father]
  • A. reactionToProphecy chosen
    Indicates how an entity responds or behaves in consequence to a given prophecy.
  • B. prophecyMade
    Indicates that a prophetic statement or prediction has been declared by one entity concerning a future event or outcome involving another entity.
  • C. prophecyFulfilled
    Indicates that a previously made prophecy has come to pass as foretold.
  • D. interpretedAsProphecyBy
    Indicates that something (such as an event, statement, or sign) is understood or treated by someone as a prophecy or predictive message about the future.
  • E. madeMajorProphecyAt
    Indicates that an entity delivered or pronounced a significant prophecy at a specific place or time.
  • 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_69e11e59db848190b4272ecd2b690ffd completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15f7b06e08190b3ca82a783965942 completed April 29, 2026, 1:31 a.m.
PD Predicate disambiguation batch_69e898cb3fb48190add6ab24a2df5822 completed April 22, 2026, 9:45 a.m.
Created at: April 16, 2026, 8:52 p.m.