Triple
T12799781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Young Outlaw |
E305983
|
entity |
| Predicate | plotMotive |
P91485
|
FINISHED |
| Object | desire for financial success |
—
|
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: desire for financial success | Statement: [The Young Outlaw, plotMotive, desire for financial success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotMotive Context triple: [The Young Outlaw, plotMotive, desire for financial success]
-
A.
motive
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
B.
hasMotiveOfCriminals
Indicates that the specified motive is attributed to or associated with the criminals in question.
-
C.
plotInvolvement
Indicates that an entity participates in, contributes to, or is affected by the events or storyline of a narrative work.
-
D.
allegedPlots
Indicates that one entity is accused or suspected of planning or conspiring to carry out harmful or illicit actions involving another entity.
-
E.
characterMotivation
chosen
Indicates the underlying reasons, desires, or goals that drive a character’s actions and decisions within 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6f858c8190915ede38e9a6a2df |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.