Triple
T30320845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventure of the Red Circle |
E771194
|
entity |
| Predicate | detective |
P32604
|
FINISHED |
| Object | Sherlock Holmes |
—
|
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: Sherlock Holmes | Statement: [The Adventure of the Red Circle, detective, Sherlock Holmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detective Context triple: [The Adventure of the Red Circle, detective, Sherlock Holmes]
-
A.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
-
B.
fictionalDetective
chosen
Indicates that the subject is a detective character who exists only in fiction rather than in real life.
-
C.
portrayedDetective
Indicates that one entity has played or depicted a detective character in a performance or work.
-
D.
hasClericalDetective
Indicates that an entity includes or is associated with a detective who is also a member of the clergy.
-
E.
notableSuspect
Indicates that an individual is a particularly significant or prominent suspect in relation to an event, case, or investigation.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68197aac481909b701a91af7406e5 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:52 p.m.