Triple
T8815221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Shop Channel |
E209759
|
entity |
| Predicate | offeredContentType |
P16209
|
FINISHED |
| Object | Virtual Console games |
—
|
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: Virtual Console games | Statement: [Wii Shop Channel, offeredContentType, Virtual Console games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredContentType Context triple: [Wii Shop Channel, offeredContentType, Virtual Console games]
-
A.
offersContentType
chosen
Indicates that one entity provides or makes available content of a specified type to another entity or context.
-
B.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
C.
offeredConfiguration
Indicates that one entity presents or makes available a specific configuration or setup option to another entity.
-
D.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
E.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff2ff248190bafcafe8b3860e53 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.