Triple
T30200561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of Wisteria Lodge |
E767770
|
entity |
| Predicate | HolmesStoryOrder |
P23880
|
FINISHED |
| Object | late Holmes story |
—
|
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: late Holmes story | Statement: [The Adventure of Wisteria Lodge, HolmesStoryOrder, late Holmes story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HolmesStoryOrder Context triple: [The Adventure of Wisteria Lodge, HolmesStoryOrder, late Holmes story]
-
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.
numberInHolmesNovels
Indicates that a given number is the count of occurrences or instances of something within the set of Holmes novels.
-
C.
firstMystery
Indicates that something is the earliest or initial instance within a set whose nature or details are unknown or unspecified.
-
D.
numberOfMysteries
Indicates the quantity or count of mysteries associated with a given entity.
-
E.
chronologicalOrderInSeries
chosen
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
- 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_69f67fc44bbc8190a5ec851757ff2ebd |
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.