Triple
T6589960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Marvyn |
E159326
|
entity |
| Predicate | majorPlotPoint |
P71660
|
FINISHED |
| Object | presumed death |
—
|
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: presumed death | Statement: [James Marvyn, majorPlotPoint, presumed death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorPlotPoint Context triple: [James Marvyn, majorPlotPoint, presumed death]
-
A.
centralPlotDevice
Indicates that one entity functions as the main narrative mechanism or element around which the plot of the other entity is structured.
-
B.
majorFlashpointIn
Indicates that an event, issue, or conflict serves as a primary source of tension or confrontation within a specified larger context or setting.
-
C.
majorExposition
Indicates that an entity is a primary or large-scale public presentation or exhibition of another entity (such as a work, collection, or topic).
-
D.
majorEpic
Indicates that an entity is a principal or most significant epic work associated with another entity (such as an author, tradition, or corpus).
-
E.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c07bb434819096ec3e3b966042a5 |
completed | March 27, 2026, 5:38 p.m. |
Created at: March 27, 2026, 1:55 p.m.