Triple
T36042656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Case of the Bizarre Bouquets |
E1042581
|
entity |
| Predicate | featuresSiblingOf |
P207143
|
FINISHED |
| Object | Sherlock Holmes |
E5614
|
NE 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: Sherlock Holmes | Statement: [The Case of the Bizarre Bouquets, featuresSiblingOf, Sherlock Holmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSiblingOf Context triple: [The Case of the Bizarre Bouquets, featuresSiblingOf, Sherlock Holmes]
-
A.
sibling
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
-
B.
siblingBranch
Indicates that two branches share the same immediate parent node in a hierarchical structure, making them parallel or peer branches.
-
C.
creatorSiblingOf
Indicates that the creator of one entity is a sibling (brother or sister) of the creator of another entity.
-
D.
bearerSibling
Indicates that the related entity is a sibling (sharing at least one parent) of the bearer entity.
-
E.
stepSibling
Indicates that two people share at least one parent but do not share both biological parents, making them step-siblings.
- F. None of above. chosen
Provenance (5 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d53119cc81908f22600a7ca92c65 |
completed | June 22, 2026, 6:24 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.