Triple
T28660479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMUR-TV |
E725453
|
entity |
| Predicate | digitalBroadcastStatus |
P144449
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [WMUR-TV, digitalBroadcastStatus, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalBroadcastStatus Context triple: [WMUR-TV, digitalBroadcastStatus, active]
-
A.
broadcastStatus
Indicates the current state or phase of a broadcast (e.g., scheduled, live, paused, or completed) in relation to the entities involved.
-
B.
hasBroadcastStatus
chosen
Indicates the current broadcast-related state or condition of an item, such as whether it is scheduled, live, completed, or unavailable.
-
C.
televisionServiceStatus
Indicates the operational or subscription state of a television service for an entity.
-
D.
broadcastNetworkType
Indicates the type or category of broadcast network through which content is transmitted or distributed.
-
E.
binaryStatus
Indicates that something has one of two possible states or conditions, typically representing a simple on/off or true/false status.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:57 a.m.