Triple
T33262509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Dunham: A Very Special Christmas Special |
E851552
|
entity |
| Predicate | hasVentriloquism |
P178098
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jeff Dunham: A Very Special Christmas Special, hasVentriloquism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVentriloquism Context triple: [Jeff Dunham: A Very Special Christmas Special, hasVentriloquism, true]
-
A.
hasVentriloquistDummy
Indicates that an entity possesses or is associated with a ventriloquist dummy.
-
B.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
C.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
-
D.
hasVoicing
Indicates that one sound, segment, or phoneme is characterized by the presence or absence of vocal fold vibration (voicing) in relation to another or to a specified voicing property.
-
E.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
- F. None of above. chosen
Provenance (4 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:32 a.m.