Triple
T19998825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirty Jobs |
E494264
|
entity |
| Predicate | notableEpisodeTypes |
P138291
|
FINISHED |
| Object | waste management jobs |
—
|
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: waste management jobs | Statement: [Dirty Jobs, notableEpisodeTypes, waste management jobs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEpisodeTypes Context triple: [Dirty Jobs, notableEpisodeTypes, waste management jobs]
-
A.
notableEpisode
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
-
B.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
C.
notableEpisodeEvent
Indicates that an event is especially significant or noteworthy within the context of a particular episode.
-
D.
notableEP
Indicates that an entity is especially well-known or significant for a particular EP (extended play recording).
-
E.
notableEpisodeTopics
Indicates that there is a notable or significant topic discussed in a particular episode.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a09bdc819083305b08a11c6e34 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:32 p.m.