Triple
T30532412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsukimonogatari |
E777039
|
entity |
| Predicate | animeBroadcastBlock |
P57046
|
FINISHED |
| Object | New Year’s Eve special |
—
|
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: New Year’s Eve special | Statement: [Tsukimonogatari, animeBroadcastBlock, New Year’s Eve special]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animeBroadcastBlock Context triple: [Tsukimonogatari, animeBroadcastBlock, New Year’s Eve special]
-
A.
animeBlock
Indicates that one entity is a programming block or time slot dedicated to airing anime content on or by another entity.
-
B.
airedInSyndication
Indicates that a media work has been broadcast or distributed for repeated showing, typically on multiple channels or platforms, beyond its original airing.
-
C.
airedOnProgrammingBlock
chosen
Indicates that a program was broadcast as part of a specific programming block or segment on a channel or platform.
-
D.
animeFormat
Indicates the specific production or release format in which an anime is presented (e.g., TV series, movie, OVA, etc.).
-
E.
tvNetworkJapan
Indicates that one entity is a television network that operates in or is associated with Japan.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:18 p.m.