Triple
T20778355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptus |
E511412
|
entity |
| Predicate | childrenMarriedTo |
P132316
|
FINISHED |
| Object | daughters of Danaus |
—
|
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: daughters of Danaus | Statement: [Egyptus, childrenMarriedTo, daughters of Danaus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childrenMarriedTo Context triple: [Egyptus, childrenMarriedTo, daughters of Danaus]
-
A.
resultedInMarriageTo
Indicates that one event, action, or circumstance led to or caused a marriage to occur between the related entities.
-
B.
spouseOfChildren
chosen
Indicates that one entity is the spouse (husband or wife) of the children of another entity.
-
C.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
D.
connectedThroughMarriageVia
Indicates that two entities are related to each other by a marital connection that is mediated through one or more intermediate spouses or in-laws, rather than by a direct marriage between them.
-
E.
houseByMarriage
Indicates a familial or household relationship established through marriage rather than by blood or direct residence.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26d34bc81908bb22087d434322d |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.