Triple
T30078521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherlock Holmes and the Spider Woman |
E764390
|
entity |
| Predicate | featuresFemmeFatale |
P115038
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sherlock Holmes and the Spider Woman, featuresFemmeFatale, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFemmeFatale Context triple: [Sherlock Holmes and the Spider Woman, featuresFemmeFatale, true]
-
A.
hasFemmeFataleCharacter
chosen
Indicates that a work includes a femme fatale character who plays a significant role in the narrative.
-
B.
femaleFeature
Indicates that the subject possesses a characteristic or attribute that is typically associated with females.
-
C.
featuresMortal
Indicates that one entity includes, presents, or prominently involves a mortal being as part of its content, composition, or subject matter.
-
D.
funzioneDellaDonna
Indicates a relationship where a role, duty, or function is specifically associated with a woman.
-
E.
femaleFigure2Attribute
Indicates that a female figure is associated with a particular attribute or characteristic.
- 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_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: April 29, 2026, 7:02 p.m.