Triple
T31352288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGS |
E799629
|
entity |
| Predicate | fictionalNetworkShowType |
P69830
|
FINISHED |
| Object | late-night sketch comedy show |
—
|
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: late-night sketch comedy show | Statement: [TGS, fictionalNetworkShowType, late-night sketch comedy show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalNetworkShowType Context triple: [TGS, fictionalNetworkShowType, late-night sketch comedy show]
-
A.
fictionalBroadcastType
Indicates that the relationship specifies the type or category of a fictional broadcast associated with an entity.
-
B.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
-
C.
hasFictionalProductionType
chosen
Indicates that an entity is associated with a specific type or category of fictional production (such as a genre, format, or style).
-
D.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
E.
hasFictionalShowWithinShow
Indicates that one show contains or features another fictional show within its narrative.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 29, 2026, 9:17 p.m.