Triple
T37230018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ren & Stimpy Show |
E923104
|
entity |
| Predicate | ratingIssuesWith |
P187324
|
FINISHED |
| Object | Standards and Practices at Nickelodeon |
—
|
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: Standards and Practices at Nickelodeon | Statement: [The Ren & Stimpy Show, ratingIssuesWith, Standards and Practices at Nickelodeon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratingIssuesWith Context triple: [The Ren & Stimpy Show, ratingIssuesWith, Standards and Practices at Nickelodeon]
-
A.
ratingContext
Indicates the situational or contextual factors under which a rating is given or applies.
-
B.
rating
Indicates an evaluation relationship where one entity assigns a qualitative or quantitative score or judgment to another entity.
-
C.
ratingContent
Indicates that an entity evaluates or assigns a quality or satisfaction score to some content.
-
D.
ratingDescription
Indicates the textual explanation or qualitative summary associated with a given rating or score.
-
E.
ratingOfWork
Indicates the evaluative score or assessment assigned to a particular work or creation.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb41333b548190912cb238ffc271c9 |
completed | May 6, 2026, 1:25 p.m. |
Created at: May 3, 2026, 4:15 p.m.