Triple
T13787920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KICU-TV |
E331312
|
entity |
| Predicate | callSignChange |
P111467
|
FINISHED |
| Object | KGSC-TV to KICU-TV |
—
|
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: KGSC-TV to KICU-TV | Statement: [KICU-TV, callSignChange, KGSC-TV to KICU-TV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignChange Context triple: [KICU-TV, callSignChange, KGSC-TV to KICU-TV]
-
A.
callSignNumber
Indicates the specific identifying number assigned as a call sign to an entity for communication or identification purposes.
-
B.
callSignStatus
Indicates the current operational or regulatory state associated with an entity’s call sign, such as whether it is active, reserved, expired, or otherwise designated.
-
C.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
D.
callSignScope
Indicates that a particular call sign is valid, applicable, or in effect only within a specified scope, context, or jurisdiction.
-
E.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
- 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_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. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.