Triple
T18629958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aida (character) |
E455385
|
entity |
| Predicate | finalFateInStory |
P101514
|
FINISHED |
| Object | dies with Radamès |
—
|
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: dies with Radamès | Statement: [Aida (character), finalFateInStory, dies with Radamès]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalFateInStory Context triple: [Aida (character), finalFateInStory, dies with Radamès]
-
A.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
B.
concludesStoryOf
Indicates that one entity brings the narrative or storyline of another entity to an end.
-
C.
fictionalOutcome
Indicates that an event, action, or situation leads to a result that occurs only within a fictional, imagined, or non-real context.
-
D.
statusAtEndOfNovel
Indicates the final state or condition of an entity as it stands at the conclusion of the novel.
-
E.
characterArcOutcome
chosen
Indicates the resulting change, resolution, or final state of a character’s personal journey or development over the course of a narrative.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f06f4a081909b64f33814577488 |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.