Triple
T875280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evening Kvartal |
E18903
|
entity |
| Predicate | hasGenreElement |
P8464
|
FINISHED |
| Object | improvisational 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: improvisational comedy | Statement: [Evening Kvartal, hasGenreElement, improvisational comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreElement Context triple: [Evening Kvartal, hasGenreElement, improvisational comedy]
-
A.
hasGenreStrength
Indicates that something possesses a particular intensity or degree of emphasis associated with a specific genre.
-
B.
hasArtisticGenre
chosen
Indicates that an entity (such as a work or creation) belongs to or is characterized by a particular artistic genre.
-
C.
genreRestriction
Indicates that there is a limitation or constraint on which genres are allowed or applicable in a given context.
-
D.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
E.
genreDiversity
Indicates the extent to which an entity involves, includes, or spans multiple distinct genres rather than being confined to a single 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acae12948190923d31966c26a130 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.