Triple
T33749223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Rock Enterprises |
E864789
|
entity |
| Predicate | hasPrimaryGenreInProductions |
P87617
|
FINISHED |
| Object | comedy |
—
|
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: comedy | Statement: [Chris Rock Enterprises, hasPrimaryGenreInProductions, comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryGenreInProductions Context triple: [Chris Rock Enterprises, hasPrimaryGenreInProductions, comedy]
-
A.
hasGenreOfWorkItAppearsIn
Indicates that an entity is associated with the genre of the work in which it appears.
-
B.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
C.
genreOfProducedWorks
chosen
Indicates that one entity is the genre category to which the works produced by another entity belong.
-
D.
hasGenreAsOutput
Indicates that an entity produces, results in, or outputs a particular genre as its outcome.
-
E.
hasGivenGenreDefiningWork
Indicates that an entity has created or produced a work that is widely regarded as defining or fundamentally shaping a particular genre.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01c5c5dbb881909b19ba87a7760ee7 |
completed | May 11, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_6a01c549af98819098e0effd775b7710 |
completed | May 11, 2026, 12:02 p.m. |
Created at: May 1, 2026, 1:45 a.m.