Triple
T30345636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ufotable |
E771860
|
entity |
| Predicate | primaryDistributionPartner |
P144950
|
FINISHED |
| Object | Aniplex |
E41416
|
NE 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: Aniplex | Statement: [Ufotable, primaryDistributionPartner, Aniplex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDistributionPartner Context triple: [Ufotable, primaryDistributionPartner, Aniplex]
-
A.
hasDistributionPartners
Indicates that an entity collaborates with other entities to distribute its products or services.
-
B.
primaryPartners
chosen
Indicates that the entities are each other’s main or most significant partners in a relationship, typically implying priority or exclusivity over other partnerships.
-
C.
distributorType
Indicates the specific category or role of a distributor in relation to the distribution of a product or service.
-
D.
distributionToPartners
Indicates the allocation or transfer of resources, benefits, or proceeds from a source entity to its partner entities.
-
E.
primaryDistribution
Indicates that one entity serves as the main or principal channel through which another entity is distributed or allocated.
- F. None of above.
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_6a0204dafcc08190868a6f3eab162505 |
completed | May 11, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e7fb509988190ac2634c3a00bc251 |
completed | June 14, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a0202dc60348190a140bb9da906f5b6 |
completed | May 11, 2026, 4:25 p.m. |
Created at: April 29, 2026, 7:55 p.m.