Triple
T5192823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii U |
E117195
|
entity |
| Predicate | bundleVariant |
P455
|
FINISHED |
| Object | Basic Set |
—
|
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: Basic Set | Statement: [Wii U, bundleVariant, Basic Set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bundleVariant Context triple: [Wii U, bundleVariant, Basic Set]
-
A.
brandNameVariant
Indicates that one brand name is an alternative or variant form of another brand name, such as a spelling, regional, or stylistic variation.
-
B.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
C.
licenseBuiltVariant
Indicates that one entity is a version or model that has been constructed under a licensing agreement based on another entity.
-
D.
movieVariantName
Indicates that one movie is known by an alternative or variant name (such as a translated, regional, or re-release title).
-
E.
supportsModelVariant
Indicates that one entity is capable of operating with, being compatible with, or otherwise accommodating a specific variant of a model.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79efd16c8190b0b16278a00baecd |
completed | March 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.