Triple
T30729507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | And Then There Was Light |
E782378
|
entity |
| Predicate | hasSatireType |
P14479
|
FINISHED |
| Object | subtle satire |
—
|
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: subtle satire | Statement: [And Then There Was Light, hasSatireType, subtle satire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSatireType Context triple: [And Then There Was Light, hasSatireType, subtle satire]
-
A.
hasSatiricalTone
Indicates that something expresses its content in a mocking, ironic, or humorous way to criticize or ridicule its subject.
-
B.
hasHumorType
chosen
Indicates that an entity possesses or is characterized by a particular style, category, or type of humor.
-
C.
hasNotableSatire
Indicates that one entity is recognized for containing or exemplifying a significant satirical treatment of the other entity.
-
D.
satirizedBy
Indicates that the subject is the target or object of satire created or performed by the specified entity.
-
E.
isSatiricalCycleComponent
Indicates that something functions as a constituent part of a larger satirical cycle or series.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 8:37 p.m.