Triple
T31937325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of Medea |
E815425
|
entity |
| Predicate | relationshipToJason |
P206122
|
FINISHED |
| Object | legitimate offspring of Jason |
—
|
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: legitimate offspring of Jason | Statement: [Children of Medea, relationshipToJason, legitimate offspring of Jason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToJason Context triple: [Children of Medea, relationshipToJason, legitimate offspring of Jason]
-
A.
relationshipToJack
Indicates the specific type of personal or social connection an entity has with Jack.
-
B.
relationshipToKenny
Indicates the specific familial, social, or interpersonal connection that one entity has to Kenny.
-
C.
relationshipToJoni
Indicates the specific familial, social, or professional connection that one entity has to the person or entity named Joni.
-
D.
relationshipToMike
Indicates the specific type of personal, social, or familial relationship that an entity has with Mike.
-
E.
relationshipToTony
Indicates the specific type of relationship or connection that an entity has with Tony.
- F. None of above. chosen
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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:05 a.m.