Triple
T30348671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandai Entertainment |
E771930
|
entity |
| Predicate | successorInLicenses |
P76919
|
FINISHED |
| Object | Funimation |
—
|
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: Funimation | Statement: [Bandai Entertainment, successorInLicenses, Funimation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInLicenses Context triple: [Bandai Entertainment, successorInLicenses, Funimation]
-
A.
tookOverLicenseFrom
chosen
Indicates that one entity assumed or acquired a license previously held by another entity.
-
B.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
-
C.
previouslyLicensedAs
Indicates that an entity held a license under a different name or status at some earlier time.
-
D.
laterLicense
Indicates that one license chronologically succeeds another, coming into effect at a later time than the referenced license.
-
E.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
- 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_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 29, 2026, 7:56 p.m.