Triple
T19848079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTV |
E476923
|
entity |
| Predicate | currentBroadcastStandard |
P15170
|
FINISHED |
| Object | digital terrestrial television |
—
|
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: digital terrestrial television | Statement: [UTV, currentBroadcastStandard, digital terrestrial television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentBroadcastStandard Context triple: [UTV, currentBroadcastStandard, digital terrestrial television]
-
A.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
B.
broadcastsInFormat
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
-
C.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
D.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
-
E.
broadcastStandard
chosen
Indicates that one entity uses, supports, or is associated with a particular broadcast transmission standard (such as a TV or radio broadcasting format).
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6580ba4948190a3260f23d011cc36 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.