Triple
T33999457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TV3 |
E871774
|
entity |
| Predicate | highDefinitionSimulcast |
P154901
|
FINISHED |
| Object | TV3 HD |
—
|
NE NERFINISHED |
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: TV3 HD | Statement: [TV3, highDefinitionSimulcast, TV3 HD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highDefinitionSimulcast Context triple: [TV3, highDefinitionSimulcast, TV3 HD]
-
A.
broadcastInHighDefinition
chosen
Indicates that the content is transmitted or made available in high-definition (HD) quality.
-
B.
HDRVideo
Indicates that the video content is encoded or presented using High Dynamic Range, providing an expanded range of brightness and color compared to standard video.
-
C.
simulcastsOn
Indicates that a broadcast (such as a TV or radio program) is transmitted simultaneously on the specified channel, platform, or service.
-
D.
videoOversampling
Indicates that a video has been sampled or processed at a higher temporal or spatial resolution than the original source, typically to improve quality or enable more detailed analysis.
-
E.
videoQuality
Indicates the level or standard of clarity, resolution, and overall visual fidelity associated with a given video.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.