Triple
T31706052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of the Reigate Squire |
E809182
|
entity |
| Predicate | HolmesCompanion |
P110508
|
FINISHED |
| Object | Dr. John Watson |
—
|
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: Dr. John Watson | Statement: [The Adventure of the Reigate Squire, HolmesCompanion, Dr. John Watson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HolmesCompanion Context triple: [The Adventure of the Reigate Squire, HolmesCompanion, Dr. John Watson]
-
A.
workInSherlockHolmesCanon
Indicates that an entity is a work (e.g., story, novel, adaptation) that belongs to or is part of the Sherlock Holmes canon.
-
B.
HolmesViewOfMilverton
Indicates that Holmes holds a particular opinion, judgment, or evaluative perspective about Milverton.
-
C.
roleInSherlock
Indicates the specific role or character that an entity portrays or holds in the context of the Sherlock series or franchise.
-
D.
relationshipWithSherlock
chosen
Indicates that an entity has a specified type of personal or professional relationship with Sherlock.
-
E.
numberInHolmesNovels
Indicates that a given number is the count of occurrences or instances of something within the set of Holmes novels.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 30, 2026, 11:13 p.m.