Triple
T35007472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kids' WB |
E1009850
|
entity |
| Predicate | featuredProgramming |
P206796
|
FINISHED |
| Object | Animaniacs |
E455765
|
NE 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: Animaniacs | Statement: [Kids' WB, featuredProgramming, Animaniacs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredProgramming Context triple: [Kids' WB, featuredProgramming, Animaniacs]
-
A.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
B.
programmingCategory
Indicates that one entity is classified as a programming-related category or type for the other entity.
-
C.
programmingBy
Indicates that one entity is created, implemented, or developed through the act of programming performed by another entity.
-
D.
primaryProgramming
Indicates that one entity serves as the main or most important programming or coding language, tool, or environment used by another entity.
-
E.
providedProgramming
Indicates that one entity supplied or made available programming (such as software, code, or a program) to another entity.
- F. None of above. chosen
Provenance (5 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37bd15e42c81908d7ba800aace8f03 |
completed | June 21, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.