Triple
T30200568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of Wisteria Lodge |
E767770
|
entity |
| Predicate | investigator |
P39674
|
FINISHED |
| Object | Sherlock Holmes |
—
|
NE NERFINISHED |
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: Sherlock Holmes | Statement: [The Adventure of Wisteria Lodge, investigator, Sherlock Holmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigator Context triple: [The Adventure of Wisteria Lodge, investigator, Sherlock Holmes]
-
A.
investigativeBody
Indicates that an entity serves as an official organization or authority responsible for conducting investigations into certain matters or cases.
-
B.
notableInvestigator
chosen
Indicates that one entity is a distinguished or prominently recognized investigator or researcher associated with another entity.
-
C.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
-
D.
roleInInvestigation
Indicates that an entity holds a specific function, capacity, or responsibility within the context of a particular investigation.
-
E.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67fc5364881908f711ee6c3489b9d |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:30 p.m.