Triple
T9702741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medeus |
E234817
|
entity |
| Predicate | sharesLegacyWith |
P3438
|
FINISHED |
| Object | other children 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: other children of Jason | Statement: [Medeus, sharesLegacyWith, other children of Jason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLegacyWith Context triple: [Medeus, sharesLegacyWith, other children of Jason]
-
A.
sharesHistoryWith
chosen
Indicates that two entities have a common or overlapping past, such as shared experiences, events, or origins.
-
B.
sharesIdentityWith
Indicates that two entities are considered to have the same identity, referring to the very same underlying individual or object rather than merely being similar or related.
-
C.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
D.
sharesOwnershipWith
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
E.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d7283188190bd50e18f643ad0d3 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.