Triple
T29872015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Channels |
E758614
|
entity |
| Predicate | allowsRearrangingChannels |
P19793
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wii Channels, allowsRearrangingChannels, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsRearrangingChannels Context triple: [Wii Channels, allowsRearrangingChannels, true]
-
A.
allowsChunkReordering
Indicates that the subject permits the order of chunks or segments to be rearranged without violating the intended structure or semantics.
-
B.
channelMixing
Indicates a relationship where content, signals, or resources from multiple channels are combined, blended, or interchanged into a unified or altered output.
-
C.
canBeReorganizedBy
Indicates that one entity has the ability or authority to rearrange, restructure, or otherwise reorganize another entity.
-
D.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
E.
channelOrder
chosen
Indicates the sequence or priority assigned to channels relative to one another.
- 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_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 5:54 p.m.