Triple
T29448659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irene Adler |
E746920
|
entity |
| Predicate | describedBySherlockHolmesAs |
P179230
|
FINISHED |
| Object | the woman |
—
|
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: the woman | Statement: [Irene Adler, describedBySherlockHolmesAs, the woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedBySherlockHolmesAs Context triple: [Irene Adler, describedBySherlockHolmesAs, the woman]
-
A.
characterizesSherlockHolmesAs
Indicates how an entity portrays, describes, or defines the qualities or nature of Sherlock Holmes.
-
B.
roleInSherlock
Indicates the specific role or character that an entity portrays or holds in the context of the Sherlock series or franchise.
-
C.
workInSherlockHolmesCanon
Indicates that an entity is a work (e.g., story, novel, adaptation) that belongs to or is part of the Sherlock Holmes canon.
-
D.
hasFictionalDetective
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
E.
relationshipWithSherlock
Indicates that an entity has a specified type of personal or professional relationship with Sherlock.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 28, 2026, 3:30 p.m.