Triple
T30303367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amonasro |
E770708
|
entity |
| Predicate | fateInPlot |
P24728
|
FINISHED |
| Object | killed by Egyptian soldiers |
—
|
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: killed by Egyptian soldiers | Statement: [Amonasro, fateInPlot, killed by Egyptian soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateInPlot Context triple: [Amonasro, fateInPlot, killed by Egyptian soldiers]
-
A.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
fateInBooks
Indicates that a character’s destiny, outcome, or predetermined path is described or revealed within written works or books.
-
C.
fateInSequel
Indicates that the outcome or destiny of an entity is revealed or occurs in a subsequent work, installment, or sequel.
-
D.
eventualFate
chosen
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
E.
knowledgeOfFate
Indicates that one entity is aware of or understands the destined or predetermined outcome concerning another entity or event.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813bd6bc81909b9b3e89c5ecf129 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:49 p.m.