Triple
T8935113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Valley of Fear |
E212755
|
entity |
| Predicate | numberInHolmesNovels |
P86282
|
FINISHED |
| Object | fourth Sherlock Holmes novel |
—
|
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: fourth Sherlock Holmes novel | Statement: [The Valley of Fear, numberInHolmesNovels, fourth Sherlock Holmes novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInHolmesNovels Context triple: [The Valley of Fear, numberInHolmesNovels, fourth Sherlock Holmes novel]
-
A.
numberOfMysteries
Indicates the quantity or count of mysteries associated with a given entity.
-
B.
hasFictionalDetective
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
C.
roleInSherlock
Indicates the specific role or character that an entity portrays or holds in the context of the Sherlock series or franchise.
-
D.
numberOfDoctorWhoNovelisations
Indicates the quantity of Doctor Who novelisations associated with a given subject.
-
E.
numberOfNewMysteries
Indicates the count of newly introduced or discovered mysteries associated with an entity or context.
- F. None of above. chosen
Provenance (4 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc669138b48190a6bb4968f029a69e |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc608331f88190bcb500ff63527f8a |
completed | April 1, 2026, 12:02 a.m. |
Created at: March 30, 2026, 6:58 p.m.