Triple
T27840730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timothy |
E703670
|
entity |
| Predicate | impliedPlotElement |
P164534
|
FINISHED |
| Object | survival cannibalism |
—
|
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: survival cannibalism | Statement: [Timothy, impliedPlotElement, survival cannibalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliedPlotElement Context triple: [Timothy, impliedPlotElement, survival cannibalism]
-
A.
plotElement
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
-
B.
introducesPlotElement
Indicates that an entity brings a new story component, twist, or development into the narrative.
-
C.
impliedRight
Indicates that one party holds a right or entitlement that is not explicitly stated but is inferred from context, agreements, or established norms.
-
D.
depictionElement
Indicates that one entity is an element or component that appears within the visual or representational depiction of another entity.
-
E.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
- F. None of above. chosen
Provenance (4 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 6:02 p.m.