Triple
T38117661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Quick Draw McGraw Show |
E951833
|
entity |
| Predicate | hasSidekickOfMainCharacter |
P175227
|
FINISHED |
| Object | Baba Looey |
—
|
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: Baba Looey | Statement: [The Quick Draw McGraw Show, hasSidekickOfMainCharacter, Baba Looey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSidekickOfMainCharacter Context triple: [The Quick Draw McGraw Show, hasSidekickOfMainCharacter, Baba Looey]
-
A.
sidekickRealName
Indicates the real, non-superhero identity of a sidekick character.
-
B.
formerSidekick
Indicates that one entity previously served as a sidekick or subordinate companion to another entity, but no longer holds that role.
-
C.
hasFictionalCompanion
Indicates that one entity has another entity as its fictional companion, typically within a narrative or imaginative context.
-
D.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
E.
usesSidekick
chosen
Indicates that one entity regularly relies on or employs another entity as a supporting assistant or secondary helper in its activities.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 3, 2026, 4:21 p.m.