Triple
T9837031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombshell (1933 film) |
E239126
|
entity |
| Predicate | setGenreContext |
P20075
|
FINISHED |
| Object | screwball comedy cycle of the 1930s |
—
|
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: screwball comedy cycle of the 1930s | Statement: [Bombshell (1933 film), setGenreContext, screwball comedy cycle of the 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setGenreContext Context triple: [Bombshell (1933 film), setGenreContext, screwball comedy cycle of the 1930s]
-
A.
hasGenreAsSetting
Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
-
B.
genreContext
chosen
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
-
C.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
D.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
E.
gameGenreContext
Indicates the genre or type of game associated with a given game entity or gaming context.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb33b07688190b78a70cf535c3efc |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.