Triple
T36887104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhypes |
E911639
|
entity |
| Predicate | associatedWithMythicFounder |
P116885
|
FINISHED |
| Object | Myskellos |
E265000
|
NE 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: Myskellos | Statement: [Rhypes, associatedWithMythicFounder, Myskellos]
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 (4 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e161f9648819096543415e4da92be |
completed | June 26, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.