Triple
T8305906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WLWT |
E194461
|
entity |
| Predicate | virtualChannelNumber |
P46398
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [WLWT, virtualChannelNumber, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virtualChannelNumber Context triple: [WLWT, virtualChannelNumber, 5]
-
A.
virtualChannel
Indicates that one entity is linked to another through a non-physical, software-defined communication channel used for transmitting data or signals.
-
B.
channelNumber
chosen
Indicates the specific numeric identifier assigned to a channel within a system or medium.
-
C.
formerChannelNumber
Indicates that an entity was previously assigned or used a particular channel number before a change to its current channel designation.
-
D.
hdChannel
Indicates that a media service or content stream is provided in high-definition (HD) format.
-
E.
terminalNumber
Indicates the specific terminal identifier associated with an entity, such as a device, port, or connection point, within a larger system or network.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.