Triple
T33806945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Dunham: Beside Himself |
E866417
|
entity |
| Predicate | featuresPuppet |
P92902
|
FINISHED |
| Object | Walter |
E851546
|
NE 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: Walter | Statement: [Jeff Dunham: Beside Himself, featuresPuppet, Walter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPuppet Context triple: [Jeff Dunham: Beside Himself, featuresPuppet, Walter]
-
A.
hasPuppetCharacter
chosen
Indicates that one entity features, includes, or is associated with a particular puppet character as part of its content or composition.
-
B.
featuresFictionalProgram
Indicates that a work includes or presents a fictional program (such as a TV show, software, or in-universe broadcast) as part of its content.
-
C.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
D.
featuresCompanion
Indicates that one entity includes, presents, or is accompanied by another entity in a supporting or secondary role.
-
E.
puppetHeight
Indicates the height measurement associated with a puppet in the relationship.
- F. None of above.
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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a022348ae2881908eae1be79b6f6ff6 |
completed | May 11, 2026, 6:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36760934408190915f213ef79baa53 |
completed | June 20, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a0220beb6b08190981fb86363757517 |
completed | May 11, 2026, 6:32 p.m. |
Created at: May 1, 2026, 1:46 a.m.