Triple
T36887104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhypes |
E911639
|
entity |
| Predicate | associatedWithMythicFounder |
—
|
GENERATED |
| Object | Myskellos |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMythicFounder Context triple: [Rhypes, associatedWithMythicFounder, Myskellos]
-
A.
hasMythicFounder
chosen
Indicates that an entity is traditionally believed to have been founded or established by a legendary or mythological figure rather than a historically verified person.
-
B.
mythicAlliance
Indicates a cooperative or strategic partnership formed between entities within a legendary, mythical, or supernatural context.
-
C.
hasMythicAncestor
Indicates that an entity is descended from, or claims lineage through, a figure from myth or legend.
-
D.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
E.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
- F. None of above.
Provenance (1 batch)
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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.