Triple
T9781291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WPIX |
E237378
|
entity |
| Predicate | digitalSignal |
P90620
|
FINISHED |
| Object | UHF |
—
|
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: UHF | Statement: [WPIX, digitalSignal, UHF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalSignal Context triple: [WPIX, digitalSignal, UHF]
-
A.
digitalStandard
Indicates that one entity defines, specifies, or embodies a recognized digital standard that the other entity follows, implements, or is evaluated against.
-
B.
signalTool
Indicates that one entity uses or activates a tool or mechanism to send a signal or convey information to another entity or system.
-
C.
digitalSubchannel
Indicates that one channel functions as a digital subchannel or subsidiary stream of another primary broadcast channel.
-
D.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
-
E.
signalContent
Indicates that one entity is the informational content or message carried, conveyed, or represented by a signal produced or transmitted by another entity.
- F. None of above. chosen
Provenance (4 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b23cb88190b458ab18d5f7f493 |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:27 p.m.