Triple
T8869809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Price |
E211122
|
entity |
| Predicate | roleInSherlock |
P85449
|
FINISHED |
| Object | co-composer of the score |
—
|
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: co-composer of the score | Statement: [Michael Price, roleInSherlock, co-composer of the score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSherlock Context triple: [Michael Price, roleInSherlock, co-composer of the score]
-
A.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
-
B.
hasFictionalDetective
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
C.
roleInCrime
Indicates the specific function, responsibility, or participation an entity has within the commission of a particular crime.
-
D.
questionedCharacter
Indicates that one entity directed questions or an interrogation toward another entity.
-
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. 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61257a548190955ad71f4c8704d5 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:51 p.m.