Triple
T18262341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Mortal Enemy |
E437388
|
entity |
| Predicate | protagonistAbandons |
P37690
|
FINISHED |
| Object | family wealth |
—
|
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: family wealth | Statement: [My Mortal Enemy, protagonistAbandons, family wealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistAbandons Context triple: [My Mortal Enemy, protagonistAbandons, family wealth]
-
A.
protagonistAction
Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
-
B.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
protagonistMakesPactWith
Indicates that the protagonist enters into a formal or binding agreement, often with significant consequences, with another entity.
-
D.
abandonment
chosen
Indicates the act of one party leaving, forsaking, or giving up responsibility for another party or thing.
-
E.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff76a1208190abbe6ab8720ed154 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.