Triple
T30504395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherlock 2 |
E776226
|
entity |
| Predicate | hasTitularCharacter |
P92323
|
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: [Sherlock 2, hasTitularCharacter, Sherlock Holmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitularCharacter Context triple: [Sherlock 2, hasTitularCharacter, Sherlock Holmes]
-
A.
titularCharacterOf
Indicates that one entity is the main or title character featured in the work represented by the other entity.
-
B.
hasMainTitleCharacter
chosen
Indicates that a work’s primary or main title is centered on, derived from, or explicitly names a particular character.
-
C.
isTitularSeeOf
Indicates that one ecclesiastical jurisdiction holds the honorary or formal status of being the titular see associated with another entity (such as a bishop or office).
-
D.
hasTitleCharacterTrait
Indicates that a title is associated with a specific character trait of an entity.
-
E.
hasIconicCharacter
Indicates that something is associated with a character widely recognized as emblematic or highly representative of it.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 29, 2026, 8:15 p.m.