Triple
T30343177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 86 -Eighty Six- |
E771808
|
entity |
| Predicate | animeSeriesComposition |
P168872
|
FINISHED |
| Object | Toshiya Ōno |
—
|
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: Toshiya Ōno | Statement: [86 -Eighty Six-, animeSeriesComposition, Toshiya Ōno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animeSeriesComposition Context triple: [86 -Eighty Six-, animeSeriesComposition, Toshiya Ōno]
-
A.
animationSeries
Indicates that one entity is an animation series in which the other entity appears, participates, or is otherwise featured.
-
B.
animeBlock
Indicates that one entity is a programming block or time slot dedicated to airing anime content on or by another entity.
-
C.
animeFormat
Indicates the specific production or release format in which an anime is presented (e.g., TV series, movie, OVA, etc.).
-
D.
animeProducer
Indicates that one entity is the producer responsible for creating, financing, or overseeing the production of an anime work involving the other entity.
-
E.
animeAdaptationBy
Indicates that one work is an anime adaptation created by a specific person, studio, or organization.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6820597308190a7e31f9c6cee3640 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:55 p.m.