Triple
T16753929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WJZ-FM |
E407159
|
entity |
| Predicate | broadcastClass |
P124509
|
FINISHED |
| Object | Class B |
—
|
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: Class B | Statement: [WJZ-FM, broadcastClass, Class B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastClass Context triple: [WJZ-FM, broadcastClass, Class B]
-
A.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
-
B.
broadcastVia
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
-
C.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
-
D.
broadcastFrom
Indicates that some content, signal, or message is transmitted or emitted starting at a particular source location, device, or entity.
-
E.
broadcastModel
Indicates that one entity serves as the template or source whose structure or values are replicated and applied across another entity or set of entities.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa28fd3c8190972e2e69ea7dece0 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.