Triple
T30669597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of the Second Stain |
E780757
|
entity |
| Predicate | containsPlotPoint |
P103369
|
FINISHED |
| Object | murder of Eduardo Lucas |
—
|
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: murder of Eduardo Lucas | Statement: [The Adventure of the Second Stain, containsPlotPoint, murder of Eduardo Lucas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPlotPoint Context triple: [The Adventure of the Second Stain, containsPlotPoint, murder of Eduardo Lucas]
-
A.
majorPlotPoint
Indicates that an event or development plays a central, pivotal role in the overall progression or outcome of the plot.
-
B.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
-
C.
partOfPlot
chosen
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
D.
hasAdventurePlot
Indicates that a work’s storyline centers on an adventure, typically involving exciting, risky, or exploratory events and journeys.
-
E.
hasMinimalPlot
Indicates that a work’s storyline is very simple, sparse, or lacking in substantial narrative development.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: April 29, 2026, 8:31 p.m.