Triple
T28635016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3.3 Story Television |
E724753
|
entity |
| Predicate | digitalChannelNumber |
P46398
|
FINISHED |
| Object | 3.3 |
—
|
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: 3.3 | Statement: [3.3 Story Television, digitalChannelNumber, 3.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalChannelNumber Context triple: [3.3 Story Television, digitalChannelNumber, 3.3]
-
A.
digitalChannelType
Indicates the type or category of digital channel through which an interaction, communication, or transaction occurs.
-
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.
fictionalChannelNumber
Indicates that a channel is assigned a number that does not correspond to a real, physically existing broadcast or transmission channel.
-
E.
digitalProvider
Indicates that one entity serves as the supplier or source of digital services, content, or infrastructure for another entity.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:39 a.m.