Triple
T11488568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamus Award |
E272344
|
entity |
| Predicate | notableTypeOfFiction |
P22130
|
FINISHED |
| Object | private eye fiction |
—
|
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: private eye fiction | Statement: [Shamus Award, notableTypeOfFiction, private eye fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTypeOfFiction Context triple: [Shamus Award, notableTypeOfFiction, private eye fiction]
-
A.
fictionalGenre
Indicates that a work of fiction belongs to or is categorized under a particular narrative genre or style.
-
B.
literatureType
Indicates the specific category or genre of literature that characterizes or classifies a given work or text.
-
C.
literaryGenreOfWork
chosen
Indicates that a work belongs to or is classified under a particular literary genre.
-
D.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
E.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a20df608190992543b4d7006f8a |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.