Triple
T31937268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of Jason |
E815424
|
entity |
| Predicate | motherOfTisander |
P161277
|
FINISHED |
| Object | Medea |
—
|
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: Medea | Statement: [Children of Jason, motherOfTisander, Medea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherOfTisander Context triple: [Children of Jason, motherOfTisander, Medea]
-
A.
motherOfPheres
Indicates that one entity is the mother (female parent) of Pheres.
-
B.
motherMother
Indicates that one entity is the mother of another entity’s mother (i.e., the maternal grandmother relationship).
-
C.
motherKunya
chosen
Indicates that one entity is the mother of another, referred to specifically by her kunya (a teknonymic nickname, typically "mother of X").
-
D.
mythicalAncestorMother
Indicates that one entity is regarded as the mythological or legendary mother-ancestor of another entity.
-
E.
motherType
Indicates the specific category or role of motherhood that one entity has in relation to another (e.g., biological, adoptive, step).
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:05 a.m.