Triple
T5601645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lachesis |
E147132
|
entity |
| Predicate | collectiveRoleWithSisters |
P64990
|
FINISHED |
| Object | control the destiny of gods and mortals |
—
|
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: control the destiny of gods and mortals | Statement: [Lachesis, collectiveRoleWithSisters, control the destiny of gods and mortals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveRoleWithSisters Context triple: [Lachesis, collectiveRoleWithSisters, control the destiny of gods and mortals]
-
A.
offspringCollectiveRole
Indicates a collective role or function that a group of offspring jointly fulfills in relation to their parent(s) or broader system.
-
B.
isEldestSisterOf
Indicates that one person is the oldest female sibling in relation to another person.
-
C.
hasSister
Indicates that one entity is the sister of another entity.
-
D.
siblingOccupation
Indicates that one person has a sibling whose job or profession is the specified occupation.
-
E.
adoptiveSister
Indicates a sisterly relationship where one person is the sister of another through legal adoption rather than biological parentage.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020dbd6dc8190ba011876c205754e |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:39 p.m.