Triple
T38643150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Queen |
E938652
|
entity |
| Predicate | appearsAsToy |
P186756
|
FINISHED |
| Object | Skylanders figure |
—
|
LITERAL 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: Skylanders figure | Statement: [Golden Queen, appearsAsToy, Skylanders figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsToy Context triple: [Golden Queen, appearsAsToy, Skylanders figure]
-
A.
isToyOf
Indicates that one entity is a toy that belongs to, is used by, or is associated with another entity.
-
B.
firstToyLineAppearance
Indicates the toy line in which an entity (such as a character or item) was first released or featured.
-
C.
toyFigureVariantOf
chosen
Indicates that one toy figure is a variant or alternate version of another toy figure, typically differing in features such as color, accessories, or minor design details while representing the same underlying character or model.
-
D.
includesToy
Indicates that one entity contains or comes with a toy as part of its contents or components.
-
E.
isToyToLifeFigure
Indicates that an object is a physical toy figure designed to be digitally activated or used within a video game or virtual environment.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:32 p.m.