Triple
T30669602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of the Second Stain |
E780757
|
entity |
| Predicate | HolmesMethod |
P169500
|
FINISHED |
| Object | deductive reasoning |
—
|
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: deductive reasoning | Statement: [The Adventure of the Second Stain, HolmesMethod, deductive reasoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HolmesMethod Context triple: [The Adventure of the Second Stain, HolmesMethod, deductive reasoning]
-
A.
detectiveMethod
chosen
Indicates that one entity uses or is associated with a particular method or technique in the context of detective work or investigation.
-
B.
notableSuspect
Indicates that an individual is a particularly significant or prominent suspect in relation to an event, case, or investigation.
-
C.
roleInSherlock
Indicates the specific role or character that an entity portrays or holds in the context of the Sherlock series or franchise.
-
D.
featuresMurderInvestigation
Indicates that the subject involves or includes a murder investigation as a central element or storyline.
-
E.
methodOfMurderScheme
Indicates the specific method or scheme by which a murder is carried out in a given situation or plan.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:31 p.m.