Triple
T25818540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mystery Series |
E650331
|
entity |
| Predicate | hasPlotType |
P105753
|
FINISHED |
| Object | suspenseful plot |
—
|
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: suspenseful plot | Statement: [The Mystery Series, hasPlotType, suspenseful plot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlotType Context triple: [The Mystery Series, hasPlotType, suspenseful plot]
-
A.
hasPlot
chosen
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
B.
hasDrawType
Indicates that an entity is associated with a specific manner, style, or category of drawing or graphical rendering.
-
C.
hasCommonPlotElement
Indicates that two narrative works share at least one similar or overlapping plot component, event, or storyline feature.
-
D.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 22, 2026, 7:27 a.m.