Triple
T36937155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mattel Interactive |
E913650
|
entity |
| Predicate | publishedGameFranchise |
P198196
|
FINISHED |
| Object | Barbie |
—
|
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: Barbie | Statement: [Mattel Interactive, publishedGameFranchise, Barbie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedGameFranchise Context triple: [Mattel Interactive, publishedGameFranchise, Barbie]
-
A.
gameFranchise
Indicates that one entity is a video game franchise to which the other entity (such as a specific game, character, or related media) belongs or is associated.
-
B.
publishedGameSeries
chosen
Indicates that a publisher has released or made available a particular game series to the public.
-
C.
franchisePlatform
Indicates that one entity serves as the platform, medium, or system through which a franchise or franchised product/service is offered, managed, or delivered.
-
D.
originalFranchiseName
Indicates that an entity is associated with the name of the franchise from which it originally comes or to which it originally belongs.
-
E.
studioFranchise
Indicates that a studio is associated with, produces, or manages a particular franchise.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:13 p.m.