Triple
T22337365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Channel 11 analog |
E552185
|
entity |
| Predicate | broadcastChannelNumber |
P46398
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Channel 11 analog, broadcastChannelNumber, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastChannelNumber Context triple: [Channel 11 analog, broadcastChannelNumber, 11]
-
A.
channelNumber
chosen
Indicates the specific numeric identifier assigned to a channel within a system or medium.
-
B.
formerChannelNumber
Indicates that an entity was previously assigned or used a particular channel number before a change to its current channel designation.
-
C.
hdChannel
Indicates that a media service or content stream is provided in high-definition (HD) format.
-
D.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
-
E.
fictionalChannelNumber
Indicates that a channel is assigned a number that does not correspond to a real, physically existing broadcast or transmission 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157804e60819094e2a903ace6f4b2 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.