Triple
T30280447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superdad |
E770074
|
entity |
| Predicate | basedInGenre |
P33225
|
FINISHED |
| Object | family 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: family comedy | Statement: [Superdad, basedInGenre, family comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInGenre Context triple: [Superdad, basedInGenre, family comedy]
-
A.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
B.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
C.
namedForGenre
Indicates that something is given a name based on or derived from a particular genre.
-
D.
coveredInGenre
chosen
Indicates that a work or item is associated with, categorized under, or treated within a particular genre.
-
E.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 29, 2026, 7:45 p.m.