Triple
T31937434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Lemnos |
E815428
|
entity |
| Predicate | familyContextOfBearer |
P47635
|
FINISHED |
| Object | Hypsipyle is daughter of Thoas |
—
|
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: Hypsipyle is daughter of Thoas | Statement: [Queen of Lemnos, familyContextOfBearer, Hypsipyle is daughter of Thoas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyContextOfBearer Context triple: [Queen of Lemnos, familyContextOfBearer, Hypsipyle is daughter of Thoas]
-
A.
familyContext
chosen
Indicates that the entities are related or associated within a family or household context, such as kinship, caregiving, or shared domestic life.
-
B.
familyApplication
Indicates that an application or request is made in the context of a family relationship, typically involving or affecting multiple family members.
-
C.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
D.
familyAssociationWith
Indicates a familial relationship or connection exists between the referenced entities.
-
E.
platformFamilyMember
Indicates that one platform is considered a member or variant within the family or group defined by another platform.
- 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_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 12:05 a.m.