Triple
T37813317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakugan Battle Brawlers |
E942707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese-Canadian co-production |
C48232
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Japanese-Canadian co-production Context triple: [Bakugan Battle Brawlers, instanceOf, Japanese-Canadian co-production]
-
A.
Japanese-American co-production
A Japanese-American co-production is a collaborative film, television, or media project jointly developed, financed, and produced by Japanese and American companies, blending creative talent, cultural perspectives, and market goals from both countries.
-
B.
Japanese Canadian
A Japanese Canadian is a person of Japanese ancestry who is a citizen or permanent resident of Canada, shaped by both Japanese heritage and Canadian society.
-
C.
Japanese-American
A Japanese-American is a person of Japanese ancestry who is a citizen or resident of the United States, shaped by both Japanese and American cultural, historical, and social influences.
-
D.
Japanese live-action film
A Japanese live-action film is a motion picture produced in Japan that features real actors and physical settings, often reflecting Japanese culture, language, and storytelling traditions.
-
E.
international co-production
chosen
An international co-production is a collaborative film or television project jointly financed, produced, and often creatively developed by production companies from two or more different countries, typically to share resources, access multiple markets, and qualify for various national incentives.
- F. None of above.
Provenance (1 batch)
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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.