Triple
T30348904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | エンジェルビーツ |
E771936
|
entity |
| Predicate | アニメーション制作 |
P7329
|
FINISHED |
| Object | P.A.WORKS |
—
|
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: P.A.WORKS | Statement: [エンジェルビーツ, アニメーション制作, P.A.WORKS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: アニメーション制作 Context triple: [エンジェルビーツ, アニメーション制作, P.A.WORKS]
-
A.
animationStudio
chosen
Indicates that one entity is an animation studio responsible for creating, producing, or animating the other entity.
-
B.
animationDirector
Indicates that one entity serves as the animation director responsible for overseeing and guiding the animation work of another entity.
-
C.
animeProducer
Indicates that one entity is the producer responsible for creating, financing, or overseeing the production of an anime work involving the other entity.
-
D.
animeAdaptationStudio
Indicates the animation studio responsible for producing the anime adaptation of a given work.
-
E.
animationStudioStyle
Indicates that one entity is characterized by, or produced in, the distinctive visual or creative style associated with a particular animation studio.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6820a250c8190ba7afa43f6f55c46 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.