Triple
T29096825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Misbehavers |
E735027
|
entity |
| Predicate | hasBellhopCharacter |
P177324
|
FINISHED |
| Object | Ted the Bellhop |
—
|
NE NERFINISHED |
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: Ted the Bellhop | Statement: [The Misbehavers, hasBellhopCharacter, Ted the Bellhop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBellhopCharacter Context triple: [The Misbehavers, hasBellhopCharacter, Ted the Bellhop]
-
A.
usesHopCharacter
Indicates that one entity employs or incorporates a hop-based character (such as a specific hop symbol, glyph, or stylistic element) in relation to another entity.
-
B.
hasPuppetCharacter
Indicates that one entity features, includes, or is associated with a particular puppet character as part of its content or composition.
-
C.
hasRescueTeamCharacter
Indicates that an entity includes or is associated with a character who is part of a rescue team.
-
D.
hasCoachCharacter
Indicates that one entity serves as the coach or trainer character associated with another entity.
-
E.
hasBailiffCharacter
Indicates that one entity is characterized as, or fulfills the role of, a bailiff in relation to another entity.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 28, 2026, 11:09 a.m.