Triple
T30078513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherlock Holmes and the Spider Woman |
E764390
|
entity |
| Predicate | portraysDrWatson |
P85449
|
FINISHED |
| Object | Nigel Bruce |
—
|
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: Nigel Bruce | Statement: [Sherlock Holmes and the Spider Woman, portraysDrWatson, Nigel Bruce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysDrWatson Context triple: [Sherlock Holmes and the Spider Woman, portraysDrWatson, Nigel Bruce]
-
A.
describedBySherlockHolmesAs
Indicates that one entity is characterized or depicted in a particular way by Sherlock Holmes.
-
B.
portrayedDetective
Indicates that one entity has played or depicted a detective character in a performance or work.
-
C.
portrayedDoctorBy
Indicates that one entity served in the role of portraying a doctor character associated with another entity (such as a show, film, or franchise).
-
D.
characterizesSherlockHolmesAs
Indicates how an entity portrays, describes, or defines the qualities or nature of Sherlock Holmes.
-
E.
roleInSherlock
chosen
Indicates the specific role or character that an entity portrays or holds in the context of the Sherlock series or franchise.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 29, 2026, 7:02 p.m.