Triple
T30349320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TBS |
E771947
|
entity |
| Predicate | notableProgramBlock |
P48038
|
FINISHED |
| Object | Animeism |
E1911690
|
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: Animeism | Statement: [TBS, notableProgramBlock, Animeism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProgramBlock Context triple: [TBS, notableProgramBlock, Animeism]
-
A.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
B.
notableBroadcast
Indicates that an entity is recognized for having made a significant or widely known broadcast.
-
C.
notableProgrammeStrand
chosen
Indicates that an entity is a significant or distinguished program series or strand associated with another entity (such as an organization, channel, or event).
-
D.
notableProgramsInclude
Indicates that the entity is known for or associated with offering or participating in the specified programs.
-
E.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
- F. None of above.
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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a278937c0e081908bbe203f8575a665 |
completed | June 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:56 p.m.