Triple
T18425724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Charles Grodin Show |
E442133
|
entity |
| Predicate | hasHostCharacteristic |
P274
|
FINISHED |
| Object | deadpan humor |
—
|
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: deadpan humor | Statement: [The Charles Grodin Show, hasHostCharacteristic, deadpan humor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostCharacteristic Context triple: [The Charles Grodin Show, hasHostCharacteristic, deadpan humor]
-
A.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
hasHostCharacter
Indicates that one entity serves as the host or primary character associated with another entity, such as a show, event, or media production.
-
C.
hasCharacteristicArtifact
Indicates that an entity is associated with a specific artifact that characterizes, exemplifies, or is typical of it.
-
D.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
E.
hasVisitorCharacteristic
Indicates that a visitor possesses or exhibits a particular characteristic, attribute, or quality.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51b12606081908ea320fd8d5554c6 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.