Triple
T31872357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of the Greek Interpreter |
E813640
|
entity |
| Predicate | MycroftRole |
P85449
|
FINISHED |
| Object | source of the case |
—
|
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: source of the case | Statement: [The Adventure of the Greek Interpreter, MycroftRole, source of the case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MycroftRole Context triple: [The Adventure of the Greek Interpreter, MycroftRole, source of the case]
-
A.
MycroftAffiliation
Indicates an affiliation or association that an entity has with the organization, group, or system named Mycroft.
-
B.
roleInSherlock
chosen
Indicates the specific role or character that an entity portrays or holds in the context of the Sherlock series or franchise.
-
C.
relationshipWithSherlock
Indicates that an entity has a specified type of personal or professional relationship with Sherlock.
-
D.
roleInMysteryMen
Indicates that one entity has a specific role or part in the context of "Mystery Men," such as in its story, production, or related work.
-
E.
characterizesSherlockHolmesAs
Indicates how an entity portrays, describes, or defines the qualities or nature of Sherlock Holmes.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:55 p.m.