Triple
T13787319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WFLD |
E331295
|
entity |
| Predicate | hasHighDefinitionBroadcasts |
P31727
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WFLD, hasHighDefinitionBroadcasts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighDefinitionBroadcasts Context triple: [WFLD, hasHighDefinitionBroadcasts, true]
-
A.
enables4KUHDOverTheAir
Indicates that one entity provides the capability for another to support or deliver 4K Ultra High Definition content via over-the-air transmission.
-
B.
hasDigitalSubchannels
Indicates that a broadcasting entity provides one or more additional digital subchannels alongside its primary digital channel.
-
C.
broadcastsInFormat
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
-
D.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
E.
hasBroadcastFeature
chosen
Indicates that an entity includes or supports a broadcast-related capability or functionality.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0249e4f88190a80316394940627d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.