Triple
T22557440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apemosyne |
E557724
|
entity |
| Predicate | fateOrderedByFather |
P115742
|
FINISHED |
| Object | to be sold or married abroad |
—
|
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: to be sold or married abroad | Statement: [Apemosyne, fateOrderedByFather, to be sold or married abroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOrderedByFather Context triple: [Apemosyne, fateOrderedByFather, to be sold or married abroad]
-
A.
fateInSequel
Indicates that the outcome or destiny of an entity is revealed or occurs in a subsequent work, installment, or sequel.
-
B.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
C.
familyFate
Indicates a relationship where the outcome, destiny, or ultimate circumstances of one entity are determined by or closely tied to those of its family or familial group.
-
D.
fateInLegend
chosen
Indicates the ultimate outcome or destiny attributed to an entity within a particular legend or mythic narrative.
-
E.
fateInFactory
Indicates that an entity meets its end, outcome, or final disposition within a factory setting.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7b06e08190b3ca82a783965942 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.