Triple
T29871991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Channels |
E758614
|
entity |
| Predicate | includesSystemChannel |
P53673
|
FINISHED |
| Object | Disc Channel |
—
|
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: Disc Channel | Statement: [Wii Channels, includesSystemChannel, Disc Channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSystemChannel Context triple: [Wii Channels, includesSystemChannel, Disc Channel]
-
A.
includesChannelType
Indicates that one entity encompasses or supports a specified type of communication or distribution channel as part of its structure or functionality.
-
B.
supportsChannels
chosen
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
C.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
D.
requiresChannel
Indicates that an entity or action depends on or must be associated with a specific communication or distribution channel in order to occur or be valid.
-
E.
isSecondaryChannelOf
Indicates that one channel functions as an additional or subordinate channel associated with a primary channel.
- 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_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: April 29, 2026, 5:54 p.m.