Triple
T33189483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6ter |
E849563
|
entity |
| Predicate | digitalTerrestrialChannelNumber |
P46398
|
FINISHED |
| Object | 22 |
—
|
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: 22 | Statement: [6ter, digitalTerrestrialChannelNumber, 22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalTerrestrialChannelNumber Context triple: [6ter, digitalTerrestrialChannelNumber, 22]
-
A.
channelNumber
chosen
Indicates the specific numeric identifier assigned to a channel within a system or medium.
-
B.
hdChannel
Indicates that a media service or content stream is provided in high-definition (HD) format.
-
C.
formerChannelNumber
Indicates that an entity was previously assigned or used a particular channel number before a change to its current channel designation.
-
D.
terrestrialChannel
Indicates that the relationship involves transmission or distribution via land-based (terrestrial) communication channels rather than satellite or other mediums.
-
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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:29 a.m.