Triple
T29020469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duff Corporation |
E737438
|
entity |
| Predicate | advertisesIn |
P33256
|
FINISHED |
| Object | Krusty the Clown Show |
—
|
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: Krusty the Clown Show | Statement: [Duff Corporation, advertisesIn, Krusty the Clown Show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advertisesIn Context triple: [Duff Corporation, advertisesIn, Krusty the Clown Show]
-
A.
advertises
Indicates that one entity promotes, publicizes, or markets another entity, typically to attract attention or customers.
-
B.
advertisedUsing
chosen
Indicates that something is promoted or made known through a particular medium, method, or channel of advertising.
-
C.
advertisedAs
Indicates that something is promoted or presented to others as having a particular quality, identity, or role.
-
D.
sponsoredIn
Indicates that one entity provides financial or material support for another entity’s participation, presence, or activity within a particular context, event, or medium.
-
E.
includesAdvertisingClause
Indicates that a contract or agreement contains a specific clause governing advertising-related rights, obligations, or restrictions.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66004da14819098b0fa2906521298 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:48 a.m.