Triple
T16612987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XERB-AM |
E403622
|
entity |
| Predicate | transmissionCategory |
P123545
|
FINISHED |
| Object | clear-channel style long-distance broadcasting |
—
|
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: clear-channel style long-distance broadcasting | Statement: [XERB-AM, transmissionCategory, clear-channel style long-distance broadcasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionCategory Context triple: [XERB-AM, transmissionCategory, clear-channel style long-distance broadcasting]
-
A.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
B.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
C.
titleTransmission
Indicates the transfer or conveyance of legal ownership or title from one party to another.
-
D.
transmissionStandard
Indicates the communication or signal protocol used to transmit data or content between systems or devices.
-
E.
transmissionFactor
Indicates how strongly or efficiently something is passed or transmitted from one entity to another.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3609776d48190b6b8c7826ac575c4 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.