Triple
T29872018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Channels |
E758614
|
entity |
| Predicate | successorInterfaceConcept |
P11238
|
FINISHED |
| Object | HOME Menu on Wii U |
—
|
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: HOME Menu on Wii U | Statement: [Wii Channels, successorInterfaceConcept, HOME Menu on Wii U]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInterfaceConcept Context triple: [Wii Channels, successorInterfaceConcept, HOME Menu on Wii U]
-
A.
successorConcept
Indicates that one concept directly follows and replaces another in a sequence, versioning, or conceptual progression.
-
B.
successorInterface
chosen
Indicates that one interface directly follows and replaces another interface in a sequence or version lineage.
-
C.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
D.
successorSpecification
Indicates that one specification is defined as the direct successor or follow-up version of another specification.
-
E.
successorInstanceOf
Indicates that one entity is a later or updated instance of another, preserving a continuity or versioned succession between them.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 29, 2026, 5:54 p.m.